# CVE-2016-0291: Command injection in n/a

> Authenticated attackers with report server access can execute arbitrary commands on IBM BigFix Platform servers.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fj48-9cfm-37x5

## What is CVE-2016-0291?

CVE-2016-0291 is a high-severity command injection vulnerability in n/a, published on 28 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM BigFix Platform 9.0, 9.1 before 9.1.8, and 9.2 before 9.2.8 allow remote authenticated users to execute arbitrary commands by leveraging report server access. IBM X-Force ID: 111302.

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

## Which versions are affected by CVE-2016-0291?

It affects 1 product.


Products: Ibm Bigfix Platform.

## How do I fix CVE-2016-0291?

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

## Is CVE-2016-0291 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6082](https://insights.sbomify.com/CVE-2016-6082/): Use after free in BigFix Platform (critical 10.0)
- [CVE-2018-1475](https://insights.sbomify.com/CVE-2018-1475/): Security feature bypass in BigFix Platform (critical 9.8)
- [CVE-2017-1221](https://insights.sbomify.com/CVE-2017-1221/): Weak cryptography in BigFix Platform (critical 9.8)
- [CVE-2019-4013](https://insights.sbomify.com/CVE-2019-4013/): File upload in BigFix Platform (critical 9.0)
- [CVE-2018-1479](https://insights.sbomify.com/CVE-2018-1479/): Cross-site request forgery in BigFix Platform (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0291 and fix it if it is affected.

What it is: CVE-2016-0291 is a high-severity command injection vulnerability in n/a, published on 28 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-0291 in the wild and no public exploit code.

Affected product: n/a. 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-2016-0291/ (Markdown: https://insights.sbomify.com/CVE-2016-0291/index.md)
```

## Sources

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

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