Unauthenticated log forgery
Published Jun 22, 2022 · Updated Aug 3, 2024
Log injection in Apache Sling Commons Log 5.4.0 and earlier and Sling API 2.25.0 and earlier allows remote attackers to forge log entries. Apache has not published the affected method or the exact path by which untrusted data reaches logging output. Network access without authentication is sufficient; forged records can conceal activity and corrupt log files, with no reported data-disclosure or code-execution impact.
Summary
What happened
Log injection in Apache Sling Commons Log 5.4.0 and earlier and Sling API 2.25.0 and earlier allows remote attackers to forge log entries. Apache has not published the affected method or the exact path by which untrusted data reaches logging output. Network access without authentication is sufficient; forged records can conceal activity and corrupt log files, with no reported data-disclosure or code-execution impact.
The record
- CVE
- CVE-2022-32549
- Published
- Jun 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Sling
- Classifications
- CWE-117, CWE-116, T1070
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 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=Apache Sling API <=2.25.0
- Affected versionversion=Apache Sling Commons Log <=5.4.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