Sensitive header disclosure via unfiltered authentication requests
Published Mar 8, 2023 · Updated Mar 4, 2025
Information exposure in GitLab DAST analyzer 2.0 through 3.0.54 allows remote attackers to obtain configured request headers. During authentication, the analyzer forwards configured headers to cross-origin stylesheet and form URLs because that step does not filter destination URLs. Exploitation requires an authenticated DAST scan configured with custom headers against an authentication page containing attacker-controlled cross-origin resources, exposing header values without altering data or service availability.
Summary
What happened
Information exposure in GitLab DAST analyzer 2.0 through 3.0.54 allows remote attackers to obtain configured request headers. During authentication, the analyzer forwards configured headers to cross-origin stylesheet and form URLs because that step does not filter destination URLs. Exploitation requires an authenticated DAST scan configured with custom headers against an authentication page containing attacker-controlled cross-origin resources, exposing header values without altering data or service availability.
The record
- CVE
- CVE-2022-4315
- Published
- Mar 8, 2023
- Updated
- Mar 4, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 8, 2023CVE publishedPublication date reported by the CVE source.
- Mar 4, 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.0, <3.0.55
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- GitLab cross-origin header-leak 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