dbcve.org
Tm Ac1900Operating system · T Mobile

CVE-2014-9583

HIGH · 10.0 CVSS v2.0 Published 2015-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges 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
common.c in infosvr in ASUS WRT firmware 3.0.0.4.376_1071, 3.0.0.376.2524-g0013f52, and other versions, as used in RT-AC66U, RT-N66U, and other routers, does not properly check the MAC address for a request, which allows remote attackers to bypass authentication and execute arbitrary commands via a NET_CMD_ID_MANU_CMD packet to UDP port 9999. NOTE: this issue was incorrectly mapped to CVE-2014-10000, but that ID is invalid due to its use as an example of the 2014 CVE ID syntax change.

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

The vulnerability exists in the infosvr (information server) component of ASUS WRT firmware. The common.c file fails to properly validate MAC addresses in incoming requests, allowing remote attackers to bypass authentication entirely. By sending a specially crafted NET_CMD_ID_MANU_CMD packet to UDP port 9999, an unauthenticated attacker can execute arbitrary commands on affected routers including RT-AC66U and RT-N66U.

MitigationApply the latest ASUS firmware update for affected router models once released. If no update is available, consider network segmentation to limit exposure of UDP port 9999 or disable the infosvr service if possible.

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
Tm Ac1900Operating system
Affected:= 3.0.0.4.376_3169
Wrt FirmwareOperating system
Affected:= 3.0.0.4.376.2524-g0012f52= 3.0.0.4.376_1071

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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
    Access router administration interface or check device labeling to confirm the exact model number (RT-AC66U, RT-N66U, or T-Mobile TM-AC1900)
    Affected if Router is NOT one of RT-AC66U, RT-N66U, or TM-AC1900 models - these are the only affected models listed
  2. Check firmware version
    Log into router web interface, look for firmware version in Administration > Firmware Version or use 'nvram get firmver' and 'nvram get buildno' via telnet/SSH if available
    Affected if Firmware version does NOT match 3.0.0.4.376_3169 (TM-AC1900), 3.0.0.4.376.2524-g0012f52, or 3.0.0.4.376_1071 - only these specific versions are affected
  3. Verify UDP port 9999 is listening
    Use a network scanner (such as nmap -sU -p 9999 target_ip) from a machine on the same network to check if the infosvr UDP port 9999 is open and responding
    Affected if UDP port 9999 is closed or not responding - the vulnerability requires this port to be accessible for exploitation
  4. Confirm infosvr service is enabled
    Access router via telnet/SSH and run 'ps | grep infosvr' or check router web interface for any 'Info Server' or 'LAN > IPTV' settings that may control this service
    Affected if The infosvr process is not running - the vulnerability only applies when this service is active
  5. Test for vulnerable packet response
    Send a NET_CMD_ID_MANU_CMD packet (magic bytes 0x0C 0x00 0x04 0x10) to UDP port 9999 using a tool like netcat or custom script and observe if any response is received without authentication
    Affected if Port 9999 responds to malformed MAC address requests - this indicates the vulnerable code path is present and exploitable

A user is affected if they run an RT-AC66U, RT-N66U, or TM-AC1900 router with firmware version 3.0.0.4.376_3169, 3.0.0.4.376.2524-g0012f52, or 3.0.0.4.376_1071 AND have UDP port 9999 exposed with infosvr service enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest ASUS firmware update for affected router models once released. If no update is available, consider network segmentation to limit exposure of UDP port 9999 or disable the infosvr service if possible.

Fix this in Tm Ac1900 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9583 — 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-2014-9583 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