Local file disclosure via external entity processing
Published Aug 16, 2022 · Updated Aug 3, 2024
XXE in Eclipse Sphinx before 0.13.1 allows remote attackers to read local files through crafted XML containing external entities. Sphinx invokes Apache Xerces with referenced external entity processing enabled, so attacker-supplied DTD definitions resolve local files and send their contents in HTTP requests. Exploitation requires unauthenticated network delivery of crafted XML to a Sphinx-based application that passes it to the vulnerable parser.
Summary
What happened
XXE in Eclipse Sphinx before 0.13.1 allows remote attackers to read local files through crafted XML containing external entities. Sphinx invokes Apache Xerces with referenced external entity processing enabled, so attacker-supplied DTD definitions resolve local files and send their contents in HTTP requests. Exploitation requires unauthenticated network delivery of crafted XML to a Sphinx-based application that passes it to the vulnerable parser.
The record
- CVE
- CVE-2022-2838
- Published
- Aug 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Eclipse Foundation
- Product
- Eclipse Sphinx
- Classifications
- CWE-611
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=0.7.0 <unspecified
- Affected versionversion=unspecified <0.13.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