# CVE-2022-2251: Command injection in GitLab Runner

> Attackers can execute arbitrary commands in GitLab Runner by crafting malicious branch names, requiring another user to trigger the pipeline.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** BIT-gitlab-runner-2022-2251, GHSA-cxfq-cc8j-j2pp, UBUNTU-CVE-2022-2251

## What is CVE-2022-2251?

CVE-2022-2251 is a medium-severity command injection vulnerability in GitLab Runner, published on 17 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper sanitization of branch names in GitLab Runner affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows a user who creates a branch with a specially crafted name and gets another user to trigger a pipeline to execute commands in the runner as that other user.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab-runner` | Bitnami | All versions | 15.3.5, 15.4.4, 15.5.2 |

Products: Gitlab Runner.

## How do I fix CVE-2022-2251?

Upgrade gitlab-runner to a fixed version for your release line: 15.3.5, 15.4.4 or 15.5.2.

## Is CVE-2022-2251 being exploited?

There is no known exploitation of CVE-2022-2251 in the wild and no public exploit code.

## Other vulnerabilities in GitLab Runner

- [CVE-2020-13327](https://insights.sbomify.com/CVE-2020-13327/): Misconfiguration in GitLab Runner (medium 6.0)
- [CVE-2020-13295](https://insights.sbomify.com/CVE-2020-13295/): Server-side request forgery in GitLab Runner (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2251 is a medium-severity command injection vulnerability in GitLab Runner, published on 17 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-2251 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab-runner (Bitnami): affected all versions; fixed in 15.3.5, 15.4.4, 15.5.2

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-2251/ (Markdown: https://insights.sbomify.com/CVE-2022-2251/index.md)
```

## Sources

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

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