CVE-2022-1423

Description

Improper access control in the CI/CD cache mechanism in GitLab CE/EE affecting all versions starting from 1.0.2 before 14.8.6, all versions from 14.9.0 before 14.9.4, and all versions from 14.10.0 before 14.10.1 allows a malicious actor with Developer privileges to perform cache poisoning leading to arbitrary code execution in protected branches

Category

7.1
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.06%
Third-Party Advisory gitlab.com Third-Party Advisory hackerone.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/330047 broken link
https://hackerone.com/reports/1182375 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1423.json third party advisory

Frequently Asked Questions

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