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

> Remote attackers on the local network can execute arbitrary commands on Cisco Meraki devices by exploiting known secrets in an HTTP handler.

- **Severity:** Medium 5.4 (`AV:A/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 24 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v7x3-c3f9-2xc9

## What is CVE-2014-7994?

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

### Official description

Cisco-Meraki MS, MR, and MX devices with firmware before 2014-09-24 allow remote attackers to execute arbitrary commands by leveraging knowledge of a cross-device secret and a per-device secret, and sending a request to an unspecified HTTP handler on the local network, aka Cisco-Meraki defect ID 00301991.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 6 products.


Products: Cisco Meraki Mr, Cisco Meraki Mr Firmware, Cisco Meraki Ms, Cisco Meraki Ms Firmware, Cisco Meraki Mx, Cisco Meraki Mx Firmware.

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

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

## Is CVE-2014-7994 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7999](https://insights.sbomify.com/CVE-2014-7999/): Privilege escalation in n/a (high 7.7)
- [CVE-2014-7995](https://insights.sbomify.com/CVE-2014-7995/): Auth bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-7994 is a medium-severity command injection vulnerability in n/a, published on 24 Dec 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-7994 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-7994/ (Markdown: https://insights.sbomify.com/CVE-2014-7994/index.md)
```

## Sources

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

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