# CVE-2014-2718: Code injection in n/a

> Man-in-the-middle attackers can execute arbitrary code on ASUS routers by providing malicious firmware updates due to missing integrity checks.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r86x-h62p-fj22

## What is CVE-2014-2718?

CVE-2014-2718 is a high-severity code injection vulnerability in n/a, published on 4 Nov 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ASUS RT-AC68U, RT-AC66R, RT-AC66U, RT-AC56R, RT-AC56U, RT-N66R, RT-N66U, RT-N56R, RT-N56U, and possibly other RT-series routers before firmware 3.0.0.4.376.x do not verify the integrity of firmware (1) update information or (2) downloaded updates, which allows man-in-the-middle (MITM) attackers to execute arbitrary code via a crafted image.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 2 products.


Products: Asus Rt Series Firmware, T-Mobile Tm-Ac1900.

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

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

## Is CVE-2014-2718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2718 is a high-severity code injection vulnerability in n/a, published on 4 Nov 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-2718 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-2718/ (Markdown: https://insights.sbomify.com/CVE-2014-2718/index.md)
```

## Sources

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

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