Local file disclosure via enabled external entities
Published May 11, 2020 · Updated Aug 5, 2024
XXE in Apache log4net before 2.0.10 allows attackers to read local data through attacker-controlled configuration files. The InternalConfigure(ILoggerRepository, Stream) path parses configuration XML without disabling external entity resolution, so declared entities can retrieve local or network resources. Exploitation requires a consuming application to accept attacker-controlled log4net configuration, and access remains bounded by the application process.
Summary
What happened
XXE in Apache log4net before 2.0.10 allows attackers to read local data through attacker-controlled configuration files. The InternalConfigure(ILoggerRepository, Stream) path parses configuration XML without disabling external entity resolution, so declared entities can retrieve local or network resources. Exploitation requires a consuming application to accept attacker-controlled log4net configuration, and access remains bounded by the application process.
The record
- CVE
- CVE-2018-1285
- Published
- May 11, 2020
- Updated
- Aug 5, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache log4net
- Classifications
- CWE-611
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=Apache log4net up to 2.0.8
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