CVE-2022-22054
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-AX56U’s login function contains a path traversal vulnerability due to its inadequate filtering for special characters in URL parameters, which allows an unauthenticated local area network attacker to access restricted system paths and download arbitrary files.
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-AX56U router's login function contains a path traversal vulnerability caused by insufficient filtering of special characters in URL parameters. An unauthenticated attacker on the local network can exploit this by using directory traversal sequences (e.g., ../) in URL parameters to access restricted system paths and download arbitrary files from the device's filesystem.
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.44266CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify router firmware versionAccess the router admin interface via web browser at the default gateway (typically 192.168.1.1) and navigate to Administration > Firmware Upgrade or similar menu to view the installed firmware version. Alternatively, check the firmware version sticker on the device or via the ASUS Router app.Affected if The installed firmware version is exactly 3.0.0.4.386.44266
-
Verify login page accessibilityAttempt to access the router login page from a computer on the local network by entering the router IP address in a web browser. Confirm the login page loads successfully.Affected if The login page is accessible without authentication from the local network, indicating the vulnerable function is exposed
-
Confirm router is on local network segmentDetermine if the router management interface is reachable from your client device by running a ping test to the router IP address and attempting an HTTP connection to port 80 or 443.Affected if The router is reachable from your client device on the same local network segment, satisfying the local network attacker requirement for exploitation
-
Check WAN exposure of management interfaceLog into the router admin panel and navigate to WAN settings or port forwarding rules. Verify if the web management interface (HTTP/HTTPS ports) is exposed to the WAN interface or if any port forwarding rules direct external traffic to the router's internal IP.Affected if The router's web interface is port-forwarded or otherwise accessible from WAN, expanding the potential attacker reach beyond local network only
You are affected if your ASUS RT-AX56U runs firmware version 3.0.0.4.386.44266 and the router login interface is accessible from a network where untrusted attackers could send crafted URL parameters containing directory traversal sequences.
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 the latest firmware update from ASUS for the RT-AX56U router. If no update is available, restrict LAN access to trusted devices only and consider network segmentation to limit exposure.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22054 — 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-22054 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