dbcve.org
Asuswrt MerlinOperating system

CVE-2017-12754

HIGH · 8.8 CVSS v3.1 Published 2017-08-09
Fix available
A fix is available. Upgrade to after 380.67 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Stack buffer overflow in httpd in Asuswrt-Merlin firmware 380.67_0RT-AC5300 and earlier for ASUS devices and ASUS firmware for ASUS RT-AC5300, RT_AC1900P, RT-AC68U, RT-AC68P, RT-AC88U, RT-AC66U, RT-AC66U_B1, RT-AC58U, RT-AC56U, RT-AC55U, RT-AC52U, RT-AC51U, RT-N18U, RT-N66U, RT-N56U, RT-AC3200, RT-AC3100, RT_AC1200GU, RT_AC1200G, RT-AC1200, RT-AC53, RT-N12HP, RT-N12HP_B1, RT-N12D1, RT-N12+, RT_N12+_PRO, RT-N16, and RT-N300 devices allows remote attackers to execute arbitrary code on the router by sending a crafted http GET request packet that includes a long delete_offline_client parameter in the url.

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 confidence

Stack buffer overflow vulnerability in the httpd web server daemon of Asuswrt-Merlin and ASUS firmware. The vulnerability is triggered by sending a crafted HTTP GET request with an excessively long delete_offline_client parameter, causing a buffer overflow on the stack and allowing remote code execution. The attack is pre-authentication, making it remotely exploitable.

MitigationUpdate router firmware to a version newer than 380.67_0 for affected ASUS devices. If patching is not immediately possible, disable remote web management or place the router behind a NAT/firewall to limit exposure to unauthenticated attackers.

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
Asuswrt MerlinOperating system
Affected:<= 380.67

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model and firmware
    Access router administration panel or check the device label/menu for model number and firmware version. For command-line access, run 'nvram get firmware_version' or 'cat /proc/version' if you have shell access.
    Affected if The device is an ASUS router running Asuswrt-Merlin or ASUS firmware with version 380.67 or lower.
  2. Check if httpd web service is running and accessible
    Attempt to access the router's web interface via HTTP/HTTPS from the network. Look for the ASUS login page at the default gateway IP address.
    Affected if The httpd web server daemon is running and responds to HTTP requests on the router's WAN or LAN interface.
  3. Verify remote web management exposure
    Check router settings under 'WAN' or 'Remote Management' settings. Look for options like 'Enable Web GUI from WAN' or 'Remote Management' that expose the httpd service to the internet.
    Affected if Remote web management (Web GUI access from WAN) is enabled, allowing unauthenticated attackers to reach the httpd service over the internet.
  4. Confirm delete_offline_client parameter availability
    Send a crafted HTTP GET request to the router's web interface with an arbitrary or empty delete_offline_client parameter, or inspect the router's web UI for client management features.
    Affected if The router's httpd supports the delete_offline_client parameter in its HTTP request handling, indicating the vulnerable code path exists.

The environment is affected if the router runs Asuswrt-Merlin or ASUS firmware version 380.67 or lower, the httpd web service is accessible (especially from WAN), and the delete_offline_client functionality is present in the web interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 380.67
Interim mitigation

Update router firmware to a version newer than 380.67_0 for affected ASUS devices. If patching is not immediately possible, disable remote web management or place the router behind a NAT/firewall to limit exposure to unauthenticated attackers.

Fix this in Asuswrt Merlin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12754 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12754 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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