Unauthorized redeployment via stale protected-environment membership
Published Aug 23, 2021 · Updated Aug 3, 2024
Improper authorization in GitLab EE allows remote authenticated users to trigger protected-environment deployments after access removal. Protected-environment membership remains stale after project removal, and the redeploy action continues to accept that retained authorization for current or earlier deployments. Exploitation requires an account that previously received explicit deployment access and can run jobs that alter or interrupt the protected environment.
Summary
What happened
Improper authorization in GitLab EE allows remote authenticated users to trigger protected-environment deployments after access removal. Protected-environment membership remains stale after project removal, and the redeploy action continues to accept that retained authorization for current or earlier deployments. Exploitation requires an account that previously received explicit deployment access and can run jobs that alter or interrupt the protected environment.
The record
- CVE
- CVE-2021-22253
- Published
- Aug 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=>=13.4, <13.12.9
- Affected versionversion=>=14.0, <14.0.7
- Affected versionversion=>=14.1, <14.1.2
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 protected-environment redeployment 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