Repository tag modification by blocked users
Published Jan 3, 2020 · Updated Aug 5, 2024
Incorrect access control in GitLab Enterprise Edition 8.2 through 12.5 allows blocked remote authenticated users to push Git tags. The tag-push authorization path fails to enforce a blocked account's revoked Git access, permitting tag updates after other Git operations are denied. Exploitation requires a previously authorized account that an administrator has blocked, and the resulting integrity impact is limited to repository tag modification.
Summary
What happened
Incorrect access control in GitLab Enterprise Edition 8.2 through 12.5 allows blocked remote authenticated users to push Git tags. The tag-push authorization path fails to enforce a blocked account's revoked Git access, permitting tag updates after other Git operations are denied. Exploitation requires a previously authorized account that an administrator has blocked, and the resulting integrity impact is limited to repository tag modification.
The record
- CVE
- CVE-2019-19263
- Published
- Jan 3, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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