Local information disclosure via detailed error messages
Published Feb 27, 2025 · Updated Feb 27, 2025
Information disclosure in IBM EntireX 11.1 allows local users to obtain sensitive information through detailed technical error messages. IBM identifies error-message generation as the locus but has not published the affected component, triggering input, or exposed data. Local low-privileged access is required, and the disclosed details can support further attacks without directly changing data or service state.
Summary
What happened
Information disclosure in IBM EntireX 11.1 allows local users to obtain sensitive information through detailed technical error messages. IBM identifies error-message generation as the locus but has not published the affected component, triggering input, or exposed data. Local low-privileged access is required, and the disclosed details can support further attacks without directly changing data or service state.
The record
- CVE
- CVE-2024-56494
- Published
- Feb 27, 2025
- Updated
- Feb 27, 2025
- Vendor
- IBM
- Product
- EntireX
- Classifications
- CWE-209
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- Feb 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo