# CVE-2017-14699: XML external entity in n/a

> Remote authenticated attackers can read arbitrary files on ASUS DSL routers via XML external entity injection in the AiCloud feature.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cj73-6r9w-rxvq

## What is CVE-2017-14699?

CVE-2017-14699 is a medium-severity vulnerability in n/a, published on 29 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple XML external entity (XXE) vulnerabilities in the AiCloud feature on ASUS DSL-AC51, DSL-AC52U, DSL-AC55U, DSL-N55U C1, DSL-N55U D1, DSL-AC56U, DSL-N10_C1, DSL-N12U C1, DSL-N12E C1, DSL-N14U, DSL-N14U-B1, DSL-N16, DSL-N16U, DSL-N17U, DSL-N66U, and DSL-AC750 routers allow remote authenticated users to read arbitrary files via a crafted DTD in (1) an UPDATEACCOUNT or (2) a PROPFIND request.

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

## Which versions are affected by CVE-2017-14699?

It affects 16 products.


Products: Asus Dsl-Ac51 Firmware, Asus Dsl-Ac52u Firmware, Asus Dsl-Ac55u Firmware, Asus Dsl-Ac56u Firmware, Asus Dsl-Ac750 Firmware, Asus Dsl-N10 C1 Firmware, Asus Dsl-N12e C1 Firmware, Asus Dsl-N12u C1 Firmware, Asus Dsl-N14u-B1 Firmware, Asus Dsl-N14u Firmware, Asus Dsl-N16 Firmware, Asus Dsl-N16u Firmware, Asus Dsl-N17u Firmware, Asus Dsl-N55u C1 Firmware, Asus Dsl-N55u D1 Firmware, Asus Dsl-N66u Firmware.

## How do I fix CVE-2017-14699?

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

## Is CVE-2017-14699 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14698](https://insights.sbomify.com/CVE-2017-14698/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-59367](https://insights.sbomify.com/CVE-2025-59367/): Auth bypass in DSL-AC51 (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14699 and fix it if it is affected.

What it is: CVE-2017-14699 is a medium-severity vulnerability in n/a, published on 29 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14699 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-2017-14699/ (Markdown: https://insights.sbomify.com/CVE-2017-14699/index.md)
```

## Sources

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

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