# CVE-2018-14713: Information disclosure in n/a

> Attackers can read arbitrary memory and CPU registers via a format string vulnerability in the router's web interface.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 13 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hwpj-2v36-69r4

## What is CVE-2018-14713?

CVE-2018-14713 is a high-severity vulnerability in n/a, published on 13 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Format string vulnerability in appGet.cgi on ASUS RT-AC3200 version 3.0.0.4.382.50010 allows attackers to read arbitrary sections of memory and CPU registers via the "hook" URL parameter.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2018-14713?

It affects 1 product.


Products: Asus Rt-Ac3200 Firmware.

## How do I fix CVE-2018-14713?

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

## Is CVE-2018-14713 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14714](https://insights.sbomify.com/CVE-2018-14714/): Command injection in n/a (critical 9.8)
- [CVE-2018-14711](https://insights.sbomify.com/CVE-2018-14711/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2018-14712](https://insights.sbomify.com/CVE-2018-14712/): Command injection in n/a (medium 6.5)
- [CVE-2018-14710](https://insights.sbomify.com/CVE-2018-14710/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14713 and fix it if it is affected.

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

## Sources

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

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