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

> Remote authenticated administrators can execute arbitrary commands on Cisco RV routers via crafted HTTP requests in the network-diagnostics interface.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9r5c-96r6-629r

## What is CVE-2014-2177?

CVE-2014-2177 is a critical command injection vulnerability in n/a, published on 7 Nov 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The network-diagnostics administration interface in the Cisco RV router firmware on RV220W devices, before 1.0.5.9 on RV120W devices, and before 1.0.4.14 on RV180 and RV180W devices allows remote authenticated users to execute arbitrary commands via a crafted HTTP request, aka Bug ID CSCuh87126.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 7 products.


Products: Cisco Rv120w, Cisco Rv120w Firmware, Cisco Rv180, Cisco Rv180 Firmware, Cisco Rv180w, Cisco Rv220w, Cisco Rv220w Firmware.

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

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

## Is CVE-2014-2177 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2178](https://insights.sbomify.com/CVE-2014-2178/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-2179](https://insights.sbomify.com/CVE-2014-2179/): File upload in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2177 is a critical command injection vulnerability in n/a, published on 7 Nov 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2177 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-2177/ (Markdown: https://insights.sbomify.com/CVE-2014-2177/index.md)
```

## Sources

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

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