Information Disclosure in github.com/traefik/traefik/v2 (CVE-2022-23469)
Summary
Vulnerability in github.com/traefik/traefik/v2 (CVE-2022-23469). Risk of unauthorized operations or information disclosure. Exploitable via Authorization header. Mitigation: upgrade to 2.9.6 or later.
Original description
The description as published by the source.
Traefik may display authorization header in the debug logs in github.com/traefik/traefik
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2022-23469 was discovered in github.com/traefik/traefik/v2.
In plain terms, it is an information exposure flaw.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/traefik/traefik/v2 CVE-2022-23469".
CVE-2022-23469 (github.com/traefik/traefik/v2). Severity: Info. Category: CWE-200.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2022-23469) in github.com/traefik/traefik/v2. In plain words, it is an information exposure flaw.
Target versions of github.com/traefik/traefik/v2 (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-200)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com