Syslog message spoofing via newline injection
Published Feb 7, 2020 · Updated Aug 7, 2024
Log injection in StatusNet through 2010 allows remote attackers to spoof syslog messages via attacker-controlled newline characters. The logging path writes attacker-controlled text to syslog without neutralizing embedded line breaks, allowing one input to create forged log records. The network path requires no authentication or user interaction, and the documented consequence is limited to log integrity.
Summary
What happened
Log injection in StatusNet through 2010 allows remote attackers to spoof syslog messages via attacker-controlled newline characters. The logging path writes attacker-controlled text to syslog without neutralizing embedded line breaks, allowing one input to create forged log records. The network path requires no authentication or user interaction, and the documented consequence is limited to log integrity.
The record
- CVE
- CVE-2010-4658
- Published
- Feb 7, 2020
- Updated
- Aug 7, 2024
- Vendor
- StatusNet, Inc.
- Product
- StatusNet
- Classifications
- CWE-74, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 7, 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=through 2010
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