Arbitrary log entry injection via unquoted request paths
Published Dec 27, 2022 · Updated Apr 11, 2025
Log injection in Gin before 1.6.0 allows remote attackers to add arbitrary entries to application logs through crafted request paths. The default Logger formatter passes the decoded request path to fmt.Sprintf with %s, so embedded newline characters become separate records. The application must use an affected Logger middleware; an encoded newline in a request path can forge trusted-looking log entries without authentication.
Summary
What happened
Log injection in Gin before 1.6.0 allows remote attackers to add arbitrary entries to application logs through crafted request paths. The default Logger formatter passes the decoded request path to fmt.Sprintf with %s, so embedded newline characters become separate records. The application must use an affected Logger middleware; an encoded newline in a request path can forge trusted-looking log entries without authentication.
The record
- CVE
- CVE-2020-36567
- Published
- Dec 27, 2022
- Updated
- Apr 11, 2025
- Vendor
- Gin-Gonic
- Product
- Gin
- Classifications
- CWE-116, CWE-117, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2022CVE publishedPublication date reported by the CVE source.
- Apr 11, 2025Record 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 <1.6.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
- Encoded-newline request-path 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