CVE-2022-25597
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 · uneditedASUS RT-AC86U’s LPD service has insufficient filtering for special characters in the user request, which allows an unauthenticated LAN attacker to perform command injection attack, execute arbitrary commands and disrupt or terminate service.
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 · high confidenceThe ASUS RT-AC86U router's LPD (Line Printer Daemon) service fails to properly sanitize special characters in user-supplied input, allowing unauthenticated LAN attackers to inject and execute arbitrary shell commands. This command injection vulnerability requires only local network access and can be exploited without authentication.
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 data= 3.0.0.4.386.45956CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify router modelCheck the router label or admin interface System Log page to confirm the device is an ASUS RT-AC86UAffected if The device is not an ASUS RT-AC86U, then it is not affected by this specific CVE
-
Check firmware versionLog into the router admin interface, navigate to Administration > Firmware Upgrade, or check the System Log page for the firmware version string 3.0.0.4.386.45956Affected if The installed firmware version is exactly 3.0.0.4.386.45956, the router is running a vulnerable version
-
Verify LPD service statusAccess the router admin interface, go to USB Application > Print Server, or inspect the running processes via telnet/ssh to the router and check if the LPD daemon (lpd or p9100d) is activeAffected if The LPD/Print Server service is enabled and running, the vulnerable service is exposed
-
Check LPD network accessibilityFrom a LAN-connected host, scan the router IP on port 515 (LPD default port) using nmap -p 515 <router_ip>, or attempt a telnet connection to port 515Affected if Port 515 is open and accepting connections from the LAN, the command injection can be exploited by any local attacker
The environment is affected if you have an ASUS RT-AC86U running firmware 3.0.0.4.386.45956 with the LPD/Print Server service enabled and accessible from the LAN.
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.
From vendor dataApply ASUS firmware updates when available; if the LPD service is unnecessary, disable it via the router admin interface; restrict LAN access to the management interface and implement network segmentation to limit attack surface.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25597 — 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-2022-25597 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