Repository read and write via unscoped LFS tokens
Published Aug 8, 2024 · Updated Sep 17, 2024
Improper authorization in affected GitLab CE/EE releases allows remote authenticated users to read and write user-owned repositories. The LFS token permission check does not restrict a token to its intended repository, allowing that token to authorize Git LFS object reads and writes elsewhere. Exploitation requires a valid low-privilege account and an LFS token; confidentiality and integrity of reachable repository data are affected, but availability is not.
Summary
What happened
Improper authorization in affected GitLab CE/EE releases allows remote authenticated users to read and write user-owned repositories. The LFS token permission check does not restrict a token to its intended repository, allowing that token to authorize Git LFS object reads and writes elsewhere. Exploitation requires a valid low-privilege account and an LFS token; confidentiality and integrity of reachable repository data are affected, but availability is not.
The record
- CVE
- CVE-2024-3035
- Published
- Aug 8, 2024
- Updated
- Sep 17, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=17.1 <17.1.4
- Affected versionversion=17.2 <17.2.2
- Affected versionversion=8.12 <17.0.6
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
No public exploit references are available in this record.
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