Credential disclosure via unredacted Authorization header
Published Feb 1, 2023 · Updated Mar 27, 2025
Information disclosure in GitLab DAST API scanner 1.6.50 through 2.0.101 allows attackers to read Authorization headers from reports. The scanner copies the configured Authorization value into vulnerability evidence and generated job artifacts instead of redacting the secret. An authenticated API scan must create a relevant finding; exposed reports can reveal credentials to report viewers or unauthenticated users of public projects.
Summary
What happened
Information disclosure in GitLab DAST API scanner 1.6.50 through 2.0.101 allows attackers to read Authorization headers from reports. The scanner copies the configured Authorization value into vulnerability evidence and generated job artifacts instead of redacting the secret. An authenticated API scan must create a relevant finding; exposed reports can reveal credentials to report viewers or unauthenticated users of public projects.
The record
- CVE
- CVE-2022-4206
- Published
- Feb 1, 2023
- Updated
- Mar 27, 2025
- Vendor
- GitLab
- Product
- API Security Testing Analyzer
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 27, 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=>=1.6.50, <2.0.102
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
- GitLab public report-artifact reproductionproof 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