CVE-2021-22253

Description

Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the necessary access to trigger deployments to protected environments under specific conditions after the access has been removed

Category

4.9
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.31%
Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/323794 broken link
https://hackerone.com/reports/1113783 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22253.json vendor advisory

Frequently Asked Questions

What is the severity of CVE-2021-22253?
CVE-2021-22253 has been scored as a medium severity vulnerability.
How to fix CVE-2021-22253?
To fix CVE-2021-22253, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2021-22253 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2021-22253 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2021-22253?
CVE-2021-22253 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.