CVE-2023-41345
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-AX55’s authentication-related function has a vulnerability of insufficient filtering of special characters within its token-generated module. An authenticated remote attacker can exploit this vulnerability to perform a Command Injection attack to execute arbitrary commands, disrupt the system, or terminate services.
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 ASUS RT-AX55 router contains a command injection vulnerability in its authentication-related token generation module. Due to insufficient filtering of special characters, an authenticated remote attacker can inject arbitrary shell commands through the token parameter, potentially achieving full system compromise.
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.51598CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check the router firmware versionLog into the ASUS RT-AX55 admin interface (typically at 192.168.1.1) and navigate to Administration > Firmware Upgrade, or check via telnet/SSH connection using 'nvram get firmware_version' or 'cat /proc/version'Affected if The installed firmware version is exactly 3.0.0.4.386.51598
-
Verify remote administration is enabledIn the admin interface, go to WAN > Basic Settings or Administration > System > Remote Management to confirm if Remote Management (Web CA/SSH/Telnet) is enabledAffected if Remote management or admin access is exposed to untrusted networks (WAN) and firmware version is 3.0.0.4.386.51598
-
Check for unexpected administrative accountsNavigate to Administration > User Account in the router interface and review all accounts for any unfamiliar admin-level users that may have been created via command injectionAffected if Unknown admin accounts exist and firmware version is 3.0.0.4.386.51598
-
Inspect router logs for suspicious activityAccess router logs via Administration > System Log and search for unusual command execution, token generation errors, or shell invocations from authentication endpointsAffected if Logs show command strings, shell executions, or repeated authentication token errors that indicate injection attempts
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 ASUS firmware update for RT-AX55 when available. As an interim measure, limit administrative access to trusted IP addresses only and monitor for unauthorized access attempts.
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41345 — 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-41345 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