CVE-2025-59365
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 · uneditedA stack buffer overflow vulnerability has been identified in certain router models. An authenticated attacker may trigger this vulnerability by sending a crafted request, potentially impacting the availability of the device. Refer to the ' Security Update for ASUS Router Firmware' section on the ASUS Security Advisory for more information.
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 confidenceStack buffer overflow vulnerability in ASUS router firmware allows an authenticated attacker to send crafted requests that can impact device availability. The vulnerability affects certain router models and requires authentication to exploit.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 the router modelAccess the router admin web interface (typically at 192.168.1.1) and navigate to 'System' or 'General' settings to view the device model name. Alternatively, check the physical device label or use 'nvram get model' via SSH/Telnet if enabled.Affected if The device is not an ASUS router (this CVE does not apply)
-
Check the installed firmware versionIn the router admin interface, go to 'Firmware Version' or 'System Information' page. The version is typically displayed as '3.0.0.4.xxxxxx' or similar. Record the full version string.Affected if No firmware version information is available or the version cannot be determined from the ASUS router interface
-
Verify if remote management is enabledIn the router admin interface, navigate to 'WAN' or 'Remote Management' settings. Check if 'Enable Web Access from WAN' or 'Allow SSH/Telnet from WAN' is turned ON.Affected if Remote management (WAN access) is enabled, exposing the authentication-required interface to external networks
-
Identify exposed management servicesFrom an external network, scan the router's public IP for open ports using 'nmap -p 80,443,8080,8443,22,23 <public-ip>' to identify accessible management interfaces.Affected if Ports 80, 443, 8080, or 8443 (HTTP/HTTPS management) are open on the WAN interface
-
Review authentication logs for anomalous requestsAccess router logs via 'System Log' or 'Log Settings' in the admin interface. Look for repeated failed login attempts, unusual POST requests, or commands from unfamiliar IP addresses.Affected if Logs show suspicious authenticated requests, especially unusual parameter values or repeated requests to the same endpoint
The environment is affected if it is an ASUS router with firmware where the specific vulnerability exists (version-dependent) and remote management or WAN-accessible admin interfaces are enabled, allowing authenticated attackers to send crafted requests.
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 security update for ASUS Router Firmware from the official ASUS Security Advisory to remediate this vulnerability.
- Consultation6.0 h
- Implementation4.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,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59365 — 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-2025-59365 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