Log forging via printed Authorization header
Published Aug 29, 2024 · Updated Aug 29, 2024
Log injection in Kitsada8621 Digital Library Management System 1.0 allows remote attackers to forge log entries via Authorization headers. JwtRefreshAuth splits the header and passes the attacker-controlled parts directly to fmt.Println, which emits embedded control characters without neutralization. Any unauthenticated request reaching this middleware can insert false application-output lines and undermine audit-log integrity.
Summary
What happened
Log injection in Kitsada8621 Digital Library Management System 1.0 allows remote attackers to forge log entries via Authorization headers. JwtRefreshAuth splits the header and passes the attacker-controlled parts directly to fmt.Println, which emits embedded control characters without neutralization. Any unauthenticated request reaching this middleware can insert false application-output lines and undermine audit-log integrity.
The record
- CVE
- CVE-2024-8297
- Published
- Aug 29, 2024
- Updated
- Aug 29, 2024
- Vendor
- Kitsada8621
- Product
- Digital Library Management System
- Classifications
- CWE-117, CWE-116, CAPEC-268, CAPEC-81, CAPEC-93, T1070
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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.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