CVE-2024-0401
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 routers supporting custom OpenVPN profiles are vulnerable to a code execution vulnerability. An authenticated and remote attacker can execute arbitrary operating system commands by uploading a crafted OVPN profile. Known affected routers include ASUS ExpertWiFi, ASUS RT-AX55, ASUS RT-AX58U, ASUS RT-AC67U, ASUS RT-AC68R, ASUS RT-AC68U, ASUS RT-AX86, ASUS RT-AC86U, ASUS RT-AX88U, and ASUS RT-AX3000.
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 confidenceAuthenticated remote attackers can execute arbitrary OS commands by uploading crafted OpenVPN profiles to vulnerable ASUS routers. The OVPN profile parser does not properly sanitize inputs, allowing command injection through specially configured profile files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm device is an ASUS routerCheck the device model through the web interface, router status page, or physical labeling. Look for ASUS model numbers (e.g., RT-AC68U, RT-AX88U, etc.)Affected if The device is not an ASUS router - this vulnerability only affects ASUS router models
-
Check if OpenVPN server feature is enabledLog into the router admin interface, navigate to VPN settings (typically under Advanced Settings > VPN), and verify if the OpenVPN server is currently enabledAffected if OpenVPN server is enabled - the vulnerability exploits the OVPN profile parser when OpenVPN is configured
-
Verify firmware version against affected rangesIn the router admin interface, go to Administration > Firmware Version (or similar) and note the installed firmware version. Compare against any ASUS security advisories for CVE-2024-0401Affected if The installed firmware version falls within the vulnerable version range and has not been patched
-
Assess remote management accessibilityCheck the router's WAN/Internet access settings. Under Administration > System > Remote Management (or similar), verify if Remote Management (Web Access from WAN) is enabledAffected if Remote management is enabled and accessible from the Internet - this expands the attack surface for authenticated attackers
-
Check authentication configurationIn the router admin interface, verify the admin account credentials are not default (default is typically admin/admin). Also check if the default admin password has been changed to a strong, unique passwordAffected if Default credentials are in use or weak password configuration - CVE-2024-0401 requires authenticated access
The user is affected if they have an ASUS router with OpenVPN enabled, a vulnerable unpatched firmware version, and the attacker can authenticate to the admin interface (especially if remote management is exposed or default credentials are in use).
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 dataRestrict access to the router administration interface, disable remote management if not required, apply vendor firmware updates when available, and use strong unique credentials for router access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0401 — 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-2024-0401 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