CVE-2022-2227

Description

Improper access control in the runner jobs API in GitLab CE/EE affecting all versions prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows a previous maintainer of a project with a specific runner to access job and project meta data under certain conditions

Category

3.1
CVSS
Severity: Low
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.12%
Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/300842 broken link
https://hackerone.com/reports/1092199 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2227.json vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-2227?
CVE-2022-2227 has been scored as a low severity vulnerability.
How to fix CVE-2022-2227?
To fix CVE-2022-2227, 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-2022-2227 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-2227 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-2022-2227?
CVE-2022-2227 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.