Pipeline triggering via exported webhook token
Published Nov 4, 2021 · Updated Aug 4, 2024
Information exposure in GitLab allows remote attackers to obtain an external webhook token embedded in a downloaded project export. The import/export configuration fails to exclude external_webhook_token from project.json, exposing the HMAC key used to authenticate mirror pull requests. The attack requires access to an export from a GitHub-connected project; the recovered key can forge a signed request that triggers CI pipelines after project access ends.
Summary
What happened
Information exposure in GitLab allows remote attackers to obtain an external webhook token embedded in a downloaded project export. The import/export configuration fails to exclude external_webhook_token from project.json, exposing the HMAC key used to authenticate mirror pull requests. The attack requires access to an export from a GitHub-connected project; the recovered key can forge a signed request that triggers CI pipelines after project access ends.
The record
- CVE
- CVE-2021-39898
- Published
- Nov 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>=10.6, <14.1.7
- Affected versionversion=>=14.2, <14.2.5
- Affected versionversion=>=14.3, <14.3.1
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.
Weakness, pattern, technique
Public exploit references
- GitLab project-export webhook-token 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