Authenticated LFS object disclosure via unchecked import linking
Published Mar 13, 2020 · Updated Aug 4, 2024
Incorrect access control in GitLab before 12.8.2 allows remote authenticated users to read LFS objects owned by other users. LFS import finalization accepts an attacker-supplied object ID and size, then links a matching object from shared storage without verifying ownership. A valid account and project-import permission are required, and the consequence is limited to disclosure of LFS object contents already stored on the instance.
Summary
What happened
Incorrect access control in GitLab before 12.8.2 allows remote authenticated users to read LFS objects owned by other users. LFS import finalization accepts an attacker-supplied object ID and size, then links a matching object from shared storage without verifying ownership. A valid account and project-import permission are required, and the consequence is limited to disclosure of LFS object contents already stored on the instance.
The record
- CVE
- CVE-2020-10081
- Published
- Mar 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 13, 2020CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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