Information disclosure and memory exhaustion via XXE
Published Jun 11, 2021 · Updated Sep 16, 2024
XXE in IBM Financial Transaction Manager 3.2.4 allows remote attackers to disclose sensitive information or exhaust memory via XML data. IBM identifies XML processing as the affected locus but does not disclose the parser, input path, or unsafe external-entity resolution operation. No authentication or user interaction is required, while high attack complexity limits reachability and the reported consequences are data disclosure and memory consumption.
Summary
What happened
XXE in IBM Financial Transaction Manager 3.2.4 allows remote attackers to disclose sensitive information or exhaust memory via XML data. IBM identifies XML processing as the affected locus but does not disclose the parser, input path, or unsafe external-entity resolution operation. No authentication or user interaction is required, while high attack complexity limits reachability and the reported consequences are data disclosure and memory consumption.
The record
- CVE
- CVE-2020-5003
- Published
- Jun 11, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Financial Transaction Manager
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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.2.4
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
No sourced classifications are available.
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