Protected-variable disclosure via unfiltered Git options
Published Oct 1, 2024 · Updated Oct 1, 2024
Improper policy enforcement in GitLab before 16.4 allows remote authenticated users to disclose protected CI/CD variables. GitLab Runner accepts unfiltered GIT_FETCH_EXTRA_FLAGS and GIT_CONFIG_* values, enabling ref substitution or a shell credential helper during repository fetch. Developer access with permission to run a protected-branch pipeline is required; successful exploitation runs attacker-selected code in the protected context and exposes its secrets.
Summary
What happened
Improper policy enforcement in GitLab before 16.4 allows remote authenticated users to disclose protected CI/CD variables. GitLab Runner accepts unfiltered GIT_FETCH_EXTRA_FLAGS and GIT_CONFIG_* values, enabling ref substitution or a shell credential helper during repository fetch. Developer access with permission to run a protected-branch pipeline is required; successful exploitation runs attacker-selected code in the protected context and exposes its secrets.
The record
- CVE
- CVE-2023-3441
- Published
- Oct 1, 2024
- Updated
- Oct 1, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-213, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2024CVE publishedPublication date reported by the CVE source.
- Oct 1, 2024Record 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=8.0 <16.4
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
- GIT_FETCH_EXTRA_FLAGS protected-pipeline reproductionfunctional · demonstrated
- GIT_CONFIG credential-helper command-injection reproductionfunctional · 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