# CVE-2016-9044: Command injection in WebFOCUS

> An authenticated attacker can execute arbitrary commands via a crafted web parameter in the WebFOCUS Business Intelligence Portal.

- **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:** 7 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rjvr-pf2g-7rjx

## What is CVE-2016-9044?

CVE-2016-9044 is a high-severity command injection vulnerability in Information Builders WebFOCUS, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An exploitable command execution vulnerability exists in Information Builders WebFOCUS Business Intelligence Portal 8.1 . A specially crafted web parameter can cause a command injection. An authenticated attacker can send a crafted web request to trigger this vulnerability.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Informationbuilders Webfocus.

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

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

## Is CVE-2016-9044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9044 is a high-severity command injection vulnerability in Information Builders WebFOCUS, published on 7 Sep 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-9044 in the wild and no public exploit code.

Affected product: Information Builders WebFOCUS. 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-9044/ (Markdown: https://insights.sbomify.com/CVE-2016-9044/index.md)
```

## Sources

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

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