Information disclosure and memory exhaustion via external entities
Published Feb 19, 2025 · Updated Aug 17, 2025
XXE in IBM Controller 11.0.0 through 11.0.1 FP3 and 11.1.0 allows remote attackers to disclose data or exhaust memory. IBM identifies XML processing as the locus but has not disclosed the parser, endpoint, or exact operation that permits external entity resolution. No authentication or user interaction is required, and exploitation can read resources available to the server process or degrade service by consuming memory.
Summary
What happened
XXE in IBM Controller 11.0.0 through 11.0.1 FP3 and 11.1.0 allows remote attackers to disclose data or exhaust memory. IBM identifies XML processing as the locus but has not disclosed the parser, endpoint, or exact operation that permits external entity resolution. No authentication or user interaction is required, and exploitation can read resources available to the server process or degrade service by consuming memory.
The record
- CVE
- CVE-2023-47160
- Published
- Feb 19, 2025
- Updated
- Aug 17, 2025
- Vendor
- IBM
- Product
- IBM Controller
- Classifications
- CWE-611, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 17, 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.0.0 <=11.0.1 changes=[{"at":"FP3","status":"affected"}]
- Affected versionversion=11.1.0
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