# CVE-2020-13327: Misconfiguration in GitLab Runner

> Insecure configuration in GitLab Runner for Kubernetes environments allows attackers to bypass security controls.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 22 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-gitlab-runner-2020-13327, GHSA-rjrm-vx9g-7gr2, UBUNTU-CVE-2020-13327

## What is CVE-2020-13327?

CVE-2020-13327 is a medium-severity vulnerability in GitLab Runner, published on 22 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue has been discovered in GitLab Runner affecting all versions starting from 13.4.0 before 13.4.2, all versions starting from 13.3.0 before 13.3.7, all versions starting from 13.2.0 before 13.2.10. Insecure Runner Configuration in Kubernetes Environments

## Which versions are affected by CVE-2020-13327?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab-runner` | Bitnami | From 13.2.0 | 13.2.10, 13.3.7, 13.4.2 |

Products: Gitlab Runner.

## How do I fix CVE-2020-13327?

Upgrade gitlab-runner to a fixed version for your release line: 13.2.10, 13.3.7 or 13.4.2.

## Is CVE-2020-13327 being exploited?

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

## Other vulnerabilities in GitLab Runner

- [CVE-2020-13295](https://insights.sbomify.com/CVE-2020-13295/): Server-side request forgery in GitLab Runner (medium 5.4)
- [CVE-2022-2251](https://insights.sbomify.com/CVE-2022-2251/): Command injection in GitLab Runner (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13327 and fix it if it is affected.

What it is: CVE-2020-13327 is a medium-severity vulnerability in GitLab Runner, published on 22 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13327 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab-runner (Bitnami): affected from 13.2.0; fixed in 13.2.10, 13.3.7, 13.4.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-2020-13327/ (Markdown: https://insights.sbomify.com/CVE-2020-13327/index.md)
```

## Sources

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

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