CVE-2022-4201: SSRF
First published: Fri Jan 27 2023(Updated: )
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.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.3.0<15.4.6 | |
| GitLab | >=11.3.0<15.4.6 | |
| GitLab | >=15.5.0<15.5.5 | |
| GitLab | >=15.5.0<15.5.5 | |
| GitLab | =15.6.0 | |
| GitLab | =15.6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-4201?
CVE-2022-4201 is classified as a high severity vulnerability due to its potential to allow unauthorized local connections.
How do I fix CVE-2022-4201?
To mitigate CVE-2022-4201, upgrade to GitLab versions 15.4.6, 15.5.5, or 15.6.1 or later.
What type of vulnerability is CVE-2022-4201?
CVE-2022-4201 is a blind Server-Side Request Forgery (SSRF) vulnerability.
Which versions of GitLab are affected by CVE-2022-4201?
CVE-2022-4201 affects GitLab versions from 11.3 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.
What can an attacker do with CVE-2022-4201?
An attacker can exploit CVE-2022-4201 to connect to local addresses when configuring a malicious GitLab Runner.
- agent/references
- agent/type
- agent/author
- agent/weakness
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/11.3.0
- version/gitlab/15.5.0
- version/gitlab/15.6.0