# CVE-2019-5485: Command Injection in gitlabhook

> Attackers can execute arbitrary commands via the repository name in the gitlabhook NPM package, requiring an upgrade to mitigate.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-549f-73hh-mj38

## What is CVE-2019-5485?

CVE-2019-5485 is a critical command injection vulnerability in gitlabhook, published on 13 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. Arbitrary commands can be injected through the repository name.

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

## Which versions are affected by CVE-2019-5485?

2 open source packages ship an affected version, including gitlabhook. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlabhook` | npm | All versions to 0.0.17 | None |
| `gitlabhook` | npm | All versions to 0.0.17 | None |

Products: Gitlabhook Project Gitlabhook.

## How do I fix CVE-2019-5485?

No fix has been published for CVE-2019-5485 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5485 being exploited?

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

Public exploit code:

- NPMJS gitlabhook 0.0.17 - 'repository' Remote Command Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5485 and fix it if it is affected.

What it is: CVE-2019-5485 is a critical command injection vulnerability in gitlabhook, published on 13 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5485 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlabhook (npm): affected all versions up to 0.0.17; no fix listed
- gitlabhook (npm): affected all versions up to 0.0.17; no fix listed

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

## Sources

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

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