# CVE-2016-6408: XML external entity in n/a

> Remote attackers can read arbitrary files in Cisco Prime Home via XML External Entity injection, requiring a patch to mitigate data disclosure risks.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6wf4-jjm2-2xr7

## What is CVE-2016-6408?

CVE-2016-6408 is a high-severity vulnerability in n/a, published on 24 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Prime Home 5.2.0 allows remote attackers to read arbitrary files via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, aka Bug ID CSCvb17814.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2016-6408?

It affects 1 product.


Products: Cisco Prime Home.

## How do I fix CVE-2016-6408?

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

## Is CVE-2016-6408 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6452](https://insights.sbomify.com/CVE-2016-6452/): Auth bypass in Cisco Prime Home before 6.0 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6408 and fix it if it is affected.

What it is: CVE-2016-6408 is a high-severity vulnerability in n/a, published on 24 Sep 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-2016-6408 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-2016-6408/ (Markdown: https://insights.sbomify.com/CVE-2016-6408/index.md)
```

## Sources

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

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