Data disclosure and memory exhaustion via XXE
Published Feb 29, 2024 · Updated Aug 2, 2024
XXE during XML processing in IBM Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 allows remote attackers to read data. The affected XML-processing path fails to restrict external entity references in attacker-supplied XML, allowing entity resolution to access sensitive resources or consume memory. A privileged product account is required, and the bounded consequences are sensitive-information disclosure or a memory-exhaustion service interruption.
Summary
What happened
XXE during XML processing in IBM Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 allows remote attackers to read data. The affected XML-processing path fails to restrict external entity references in attacker-supplied XML, allowing entity resolution to access sensitive resources or consume memory. A privileged product account is required, and the bounded consequences are sensitive-information disclosure or a memory-exhaustion service interruption.
The record
- CVE
- CVE-2023-25926
- Published
- Feb 29, 2024
- Updated
- Aug 2, 2024
- Vendor
- IBM
- Product
- IBM Guardium Key Lifecycle Manager
- Classifications
- CWE-611, T1499.003, T1005
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=3.0, 3.0.1, 4.0, 4.1, 4.1.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