Rt Ac5300 FirmwareOperating system · Asuswrt Merlin Project

CVE-2017-11344

HIGH · 7.8 CVSS v3.0 Published 2017-07-17
Fix available
A fix is available. Upgrade to after 3.0.0.4.380.7743 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Global buffer overflow in networkmap in Asuswrt-Merlin firmware 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 write shellcode at any address in the heap; this can be used to execute arbitrary code on the router by hosting a crafted device description XML document at a URL specified within a Location header in an SSDP response.

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

Buffer overflow in the networkmap service of ASUS routers allows remote attackers to write shellcode to arbitrary heap addresses via a crafted SSDP response containing a malicious URL in the Location header pointing to a malicious device description XML, enabling arbitrary code execution.

MitigationApply vendor firmware updates when available; prior to patching, disable SSDP/UPnP on affected routers and segment router management interfaces from untrusted networks to reduce attack surface.

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
Rt Ac5300 FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac1900p FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac68u FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac68p FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac88u FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac66u FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac66u B1 FirmwareOperating system
Affected:<= 3.0.0.4.380.7743
Rt Ac58u FirmwareOperating system
Affected:<= 3.0.0.4.380.7485

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 firmware version
    Log into the router web interface and navigate to 'Firmware Version' on the General page, or run `nvram get firmver` via SSH/Telnet
    Affected if firmware version is 3.0.0.4.380.7743 or lower for AC5300/AC1900P/AC68U/AC68P/AC88U/AC66U/AC66U_B1, or 3.0.0.4.380.7485 or lower for AC58U
  2. Verify networkmap service is active
    Run `ps | grep networkmap` via SSH/Telnet to see if the networkmap process is running
    Affected if the networkmap process is running (this is the vulnerable service)
  3. Confirm SSDP/UPnP is enabled
    Log into the router web interface and check 'USB Application' > 'Media Services and Router' > 'UPnP' status, or run `nvram get upnp_enable` via SSH (value of 1 means enabled)
    Affected if UPnP/SSDP is enabled (the vulnerability is exploited via crafted SSDP responses)
  4. Check for unauthorized network listeners
    Run `netstat -ulnp | grep 1900` via SSH to verify if the SSDP multicast listener (port 1900) is bound to the networkmap service
    Affected if port 1900 is listening and networkmap is bound to it (indicates the attack surface is exposed)

The router is affected if it runs a vulnerable Asuswrt Merlin firmware version (as listed) AND has the networkmap service active with SSDP/UPnP enabled, exposing the buffer overflow to remote attackers on the local network.

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 3.0.0.4.380.7743
Interim mitigation

Apply vendor firmware updates when available; prior to patching, disable SSDP/UPnP on affected routers and segment router management interfaces from untrusted networks to reduce attack surface.

Fix this in Rt Ac5300 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11344 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11344 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