# 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.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-gitlab-2022-0249, GHSA-q7f8-fr48-qw7g, UBUNTU-CVE-2022-0249

## 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 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-0249?

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 12.0.0 | 14.5.4, 14.6.4, 14.7.1 |

Products: 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.

## 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](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0249 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2022-0249 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 12.0.0; fixed in 14.5.4, 14.6.4, 14.7.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0249/ (Markdown: https://insights.sbomify.com/CVE-2022-0249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0249
- OSV: https://osv.dev/vulnerability/CVE-2022-0249

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0249/
Summaries are generated and may contain mistakes; the official description above is the record.