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

> Remote attackers can execute arbitrary OS commands in SAP TREX, requiring immediate patching to prevent system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** 27 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wgpv-w8w9-xcxp

## What is CVE-2016-6137?

CVE-2016-6137 is a critical command injection vulnerability in n/a, published on 27 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unspecified function in SAP TREX 7.10 Revision 63 allows remote attackers to execute arbitrary OS commands via unknown vectors, aka SAP Security Note 2203591.

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

It affects 1 product.


Products: Sap Trex.

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

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

## Is CVE-2016-6137 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11459](https://insights.sbomify.com/CVE-2017-11459/): Code injection in n/a (critical 9.8)
- [CVE-2017-7691](https://insights.sbomify.com/CVE-2017-7691/): Code injection in n/a (critical 9.8)
- [CVE-2016-6138](https://insights.sbomify.com/CVE-2016-6138/): Path traversal in n/a (critical 9.8)
- [CVE-2016-6139](https://insights.sbomify.com/CVE-2016-6139/): Path traversal in n/a (critical 9.8)
- [CVE-2016-6140](https://insights.sbomify.com/CVE-2016-6140/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6137 is a critical command injection vulnerability in n/a, published on 27 Sep 2016. 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-2016-6137 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-6137/ (Markdown: https://insights.sbomify.com/CVE-2016-6137/index.md)
```

## Sources

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

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