# CVE-2019-17096: Bitdefender BOX 2 bootstrap get_image_size command injection vulnerability

> An attacker can inject system commands via the bootstrap stage of Bitdefender BOX 2, potentially leading to remote code execution on the device.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/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:** 28 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xj7c-f2c8-xgv2

## What is CVE-2019-17096?

CVE-2019-17096 is a critical command injection vulnerability in Bitdefender BOX 2, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A OS Command Injection vulnerability in the bootstrap stage of Bitdefender BOX 2 allows the manipulation of the `get_image_url()` function in special circumstances to inject a system command.

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

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

It affects 2 products.


Products: Bitdefender Box 2 Firmware, Bitdefender Central.

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

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

## Is CVE-2019-17096 being exploited?

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

## Other vulnerabilities in Bitdefender BOX 2

- [CVE-2019-17102](https://insights.sbomify.com/CVE-2019-17102/): Bitdefender BOX v2 bootstrap update_setup command execution vulnerability (VA-2226) (high 8.3)
- [CVE-2019-17095](https://insights.sbomify.com/CVE-2019-17095/): Bitdefender BOX 2 bootstrap download_image command injection vulnerability (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17096 is a critical command injection vulnerability in Bitdefender BOX 2, published on 28 Jan 2020. 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-17096 in the wild and no public exploit code.

Affected product: Bitdefender BOX 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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