Credential disclosure via unredacted debug request logging
Published Dec 8, 2022 · Updated Apr 22, 2025
Information disclosure in Traefik Proxy before 2.9.6 allows attackers with log access to read Authorization credentials from debug logs. The integrated vulcand/oxy request handlers log complete HTTP request structures, including unredacted Authorization headers, at DEBUG level. Exposure requires DEBUG logging, an affected oxy-backed feature, and access to the logging system; no data modification or service interruption is reported.
Summary
What happened
Information disclosure in Traefik Proxy before 2.9.6 allows attackers with log access to read Authorization credentials from debug logs. The integrated vulcand/oxy request handlers log complete HTTP request structures, including unredacted Authorization headers, at DEBUG level. Exposure requires DEBUG logging, an affected oxy-backed feature, and access to the logging system; no data modification or service interruption is reported.
The record
- CVE
- CVE-2022-23469
- Published
- Dec 8, 2022
- Updated
- Apr 22, 2025
- Vendor
- Traefik Labs
- Product
- Traefik Proxy
- Classifications
- CWE-532, CWE-200, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=< 2.9.6
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
- GitHub Security Advisory debug-log demonstrationproof 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