# CVE-2023-47678: Missing authorization in RT-AC87U

> An attacker can read or write unauthorized files on ASUS RT-AC87U routers via TFTP due to improper access control.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 15 Nov 2023
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-8rh4-mxhq-673g

## What is CVE-2023-47678?

CVE-2023-47678 is a critical missing authorization vulnerability in ASUSTeK COMPUTER INC. RT-AC87U, published on 15 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper access control vulnerability exists in RT-AC87U all versions. An attacker may read or write files that are not intended to be accessed by connecting to a target device via tftp.

## Which versions are affected by CVE-2023-47678?

It affects 1 product.


Products: Asus Rt-Ac87u Firmware.

## How do I fix CVE-2023-47678?

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

## Is CVE-2023-47678 being exploited?

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

## Other vulnerabilities in ASUSTeK COMPUTER INC. RT-AC87U

- [CVE-2018-0581](https://insights.sbomify.com/CVE-2018-0581/): Cross-site scripting in RT-AC87U (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47678 and fix it if it is affected.

What it is: CVE-2023-47678 is a critical missing authorization vulnerability in ASUSTeK COMPUTER INC. RT-AC87U, published on 15 Nov 2023. 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-2023-47678 in the wild and no public exploit code.

Affected product: ASUSTeK COMPUTER INC. RT-AC87U. 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-2023-47678/ (Markdown: https://insights.sbomify.com/CVE-2023-47678/index.md)
```

## Sources

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

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