Log forgery via unsanitized login usernames
Published Jan 8, 2024 · Updated Nov 14, 2024
Log injection in pyLoad before 0.5.0b3.dev77 allows remote attackers to forge log entries through a crafted login username. The WebUI login handlers write the supplied username into failed-login messages without escaping CR or LF delimiters. No authentication or user interaction is required; forged entries can corrupt audit evidence, hide activity, or falsely attribute actions.
Summary
What happened
Log injection in pyLoad before 0.5.0b3.dev77 allows remote attackers to forge log entries through a crafted login username. The WebUI login handlers write the supplied username into failed-login messages without escaping CR or LF delimiters. No authentication or user interaction is required; forged entries can corrupt audit evidence, hide activity, or falsely attribute actions.
The record
- CVE
- CVE-2024-21645
- Published
- Jan 8, 2024
- Updated
- Nov 14, 2024
- Vendor
- pyLoad
- Product
- pyLoad
- Classifications
- CWE-74
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 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=< 0.5.0b3.dev77
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
- Upstream failed-login newline injection proof of conceptproof of concept · demonstrated
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