Trigger-token disclosure via overinclusive project exports
Published Oct 5, 2021 · Updated Aug 4, 2024
Information exposure in affected GitLab releases starting with 8.9 allows remote authenticated users to read trigger tokens from project exports. The export configuration includes the triggers association, causing project.json to serialize plaintext tokens belonging to other maintainers. A project Maintainer must generate and download the export; a disclosed token can impersonate its owner to run pipelines with that owner's project access.
Summary
What happened
Information exposure in affected GitLab releases starting with 8.9 allows remote authenticated users to read trigger tokens from project exports. The export configuration includes the triggers association, causing project.json to serialize plaintext tokens belonging to other maintainers. A project Maintainer must generate and download the export; a disclosed token can impersonate its owner to run pipelines with that owner's project access.
The record
- CVE
- CVE-2021-39869
- Published
- Oct 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 5, 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=>=14.2, <14.2.5
- Affected versionversion=>=14.3, <14.3.1
- Affected versionversion=>=8.9, <14.1.7
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 project-export trigger-token disclosure 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