CVE-2023-47678
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe RT-AC87U router has an improper access control vulnerability in its TFTP service. An unauthenticated attacker can read or write arbitrary files on the device by connecting via TFTP, exploiting the lack of proper access restrictions on the service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is RT-AC87UCheck the router label or web interface (typically at 192.168.1.1) for the exact model number under System or Administration settingsAffected if Device model is Asus RT-AC87U
-
Verify TFTP service statusLog into router web interface and check under Administration > System > TFTP Service or similar path depending on firmware version. Look for an enable/disable toggle for TFTPAffected if TFTP service is currently enabled on the router
-
Check TFTP service accessibilityFrom an external network (not from within LAN), attempt to connect to the router's IP on TFTP port 69, or check firewall/port forwarding rules in router settings for port 69 (UDP)Affected if TFTP port 69 is open to untrusted networks or the router allows TFTP connections from WAN
-
Inspect TFTP configurationAccess router via SSH or telnet if enabled and check /etc/tftp.conf or similar TFTP config files, or check through the web UI for TFTP share/directory settingsAffected if TFTP service has no IP access restrictions configured or permits anonymous read/write access
You are affected if you own an RT-AC87U router with TFTP service enabled and accessible, regardless of firmware version since all versions are vulnerable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply available firmware updates from ASUS for the RT-AC87U. If no update is available, disable the TFTP service if not required, or implement network-based filtering to restrict TFTP access to trusted IP addresses only.
- This vulnerability has no available fix. The RT-AC87U is an end-of-life device with no firmware updates available.
- Disable TFTP service on the device if possible through web interface or CLI.
- If TFTP cannot be disabled, implement network segmentation to restrict access to the device's management interface.
- Consider replacing the end-of-life router with a currently supported model.
- Monitor vendor security advisories for any future updates (unlikely for this legacy device).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47678 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47678 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data