Authenticated insertion of forged log entries
Published Jan 7, 2022 · Updated Aug 3, 2024
Log injection in Spring Framework 5.3.0 through 5.3.13 and 5.2.18 and earlier allows remote authenticated users to add forged log entries. Spring has not disclosed the affected methods or logging sites, the accepted input forms, or the exact neutralization failure. Low-privileged network access is required, and the reported consequence is limited to log integrity with no confidentiality or availability impact.
Summary
What happened
Log injection in Spring Framework 5.3.0 through 5.3.13 and 5.2.18 and earlier allows remote authenticated users to add forged log entries. Spring has not disclosed the affected methods or logging sites, the accepted input forms, or the exact neutralization failure. Low-privileged network access is required, and the reported consequence is limited to log integrity with no confidentiality or availability impact.
The record
- CVE
- CVE-2021-22060
- Published
- Jan 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- Spring
- Product
- Spring Framework
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 7, 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=Spring Framework 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions
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