Arbitrary log-line injection via unsanitized report ID
Published Jan 24, 2020 · Updated Aug 4, 2024
Log injection in SimpleSAMLphp before 1.18.4 allows remote authenticated users to write arbitrary log lines via crafted report IDs. The www/errorreport.php handler accepts the reportID request parameter without removing newline characters, so file logging appends attacker-controlled content as new entries. Exploitation requires access to the error-report endpoint and file logging configuration; the demonstrated impact is log integrity tampering and possible indirect disclosure through forged records.
Summary
What happened
Log injection in SimpleSAMLphp before 1.18.4 allows remote authenticated users to write arbitrary log lines via crafted report IDs. The www/errorreport.php handler accepts the reportID request parameter without removing newline characters, so file logging appends attacker-controlled content as new entries. Exploitation requires access to the error-report endpoint and file logging configuration; the demonstrated impact is log integrity tampering and possible indirect disclosure through forged records.
The record
- CVE
- CVE-2020-5225
- Published
- Jan 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- SimpleSAMLphp
- Product
- SimpleSAMLphp
- Classifications
- CWE-532
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=< 1.18.4
What conditions does exploitation require?
What is affected?
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