# CVE-2014-7989: Command injection in n/a

> Local attackers can gain shell privileges on Cisco UCS B-Series blade servers by exploiting crafted ping6 or traceroute6 commands.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x9gv-2wp3-5fc7

## What is CVE-2014-7989?

CVE-2014-7989 is a medium-severity command injection vulnerability in n/a, published on 7 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco Unified Computing System on B-Series blade servers allows local users to gain shell privileges via a crafted (1) ping6 or (2) traceroute6 command, aka Bug ID CSCuq38176.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-7989?

It affects 8 products.


Products: Cisco B200 M3, Cisco B200 M4, Cisco B22 M3, Cisco B230 M2, Cisco B260 M4, Cisco B420 M3, Cisco B440 M2, Cisco B460 M4.

## How do I fix CVE-2014-7989?

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

## Is CVE-2014-7989 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7989 and fix it if it is affected.

What it is: CVE-2014-7989 is a medium-severity command injection vulnerability in n/a, published on 7 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-7989 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-2014-7989/ (Markdown: https://insights.sbomify.com/CVE-2014-7989/index.md)
```

## Sources

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

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