CVE-2022-4201

Public Exploit

Description

A blind SSRF in GitLab CE/EE affecting all from 11.3 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1 allows an attacker to connect to local addresses when configuring a malicious GitLab Runner.

Category

3.5
CVSS
Severity: Low
CVSS 3.1 •
EPSS 0.09%
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/30376 vendor advisory issue tracking exploit
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-4201.json vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-4201?
CVE-2022-4201 has been scored as a low severity vulnerability.
How to fix CVE-2022-4201?
To fix CVE-2022-4201, 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-4201 being actively exploited in the wild?
It is possible that CVE-2022-4201 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-4201?
CVE-2022-4201 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.