CVE-2022-0249 Server-side request forgery in GitLab
Attackers can perform blind Server-Side Request Forgery attacks against shared address space in GitLab, potentially accessing internal resources.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-0249?
CVE-2022-0249 is a low-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 28 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-918
Which versions are affected by CVE-2022-0249?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 12.0.0 | 14.5.4, 14.6.4, 14.7.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-0249?
Upgrade gitlab to a fixed version for your release line: 14.5.4, 14.6.4 or 14.7.1.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2022-0249 being exploited?
There is no known exploitation of CVE-2022-0249 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2022-0249, GHSA-q7f8-fr48-qw7g, UBUNTU-CVE-2022-0249.