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

> Remote attackers can execute arbitrary code by providing a crafted firmware image that exploits premature extraction before signature verification.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 8 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w6v8-ffc7-5f5p

## What is CVE-2014-8886?

CVE-2014-8886 is a high-severity code injection vulnerability in n/a, published on 8 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVM FRITZ!OS before 6.30 extracts the contents of firmware updates before verifying their cryptographic signature, which allows remote attackers to create symlinks or overwrite critical files, and consequently execute arbitrary code, via a crafted firmware image.

Weakness: CWE-310

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

It affects 1 product.


Products: Avm Fritz\! Os.

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

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

## Is CVE-2014-8886 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7242](https://insights.sbomify.com/CVE-2015-7242/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8886 is a high-severity code injection vulnerability in n/a, published on 8 Jan 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-2014-8886 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-8886/ (Markdown: https://insights.sbomify.com/CVE-2014-8886/index.md)
```

## Sources

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

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