CVE-2022-0249

Public Exploit

Description

A vulnerability was discovered in GitLab starting with version 12. GitLab was vulnerable to a blind SSRF attack since requests to shared address space were not blocked.

Category

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

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/29395 issue tracking exploit vendor advisory
https://hackerone.com/reports/579934 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-0249.json vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-0249?
CVE-2022-0249 has been scored as a low severity vulnerability.
How to fix CVE-2022-0249?
To fix CVE-2022-0249, 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-0249 being actively exploited in the wild?
It is possible that CVE-2022-0249 is being exploited or will be exploited in a near future based on public information. 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-0249?
CVE-2022-0249 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.