Skip to content
Fencer Intel
critical 10.0

CVE-2014-9583 in the critical feed json

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 o…

published 2015-01-08 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9397

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
80.2%
EPSS 80.2% chance of exploitation in 30 days, percentile 99.6%
public exploits
3
Metasploit, Exploit-DB

Summary

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.

Timeline

  1. First public exploit (Metasploit exploit/linux/misc/asus_infosvr_auth_bypass_exec)
  2. Published

Exploit prediction

80.23% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/linux/misc/asus_infosvr_auth_bypass_exec ASUS infosvr Auth Bypass Command Execution metasploit exploit, excellent rank, 2015-01-04
  • EDB-44524 ASUS infosvr - Authentication Bypass Command Execution (Metasploit) remote, 2018-04-24
  • EDB-35688 ASUSWRT 3.0.0.4.376_1071 - LAN Backdoor Command Execution remote, 2015-01-04
  • github.com https://github.com/jduck/asus-cmd referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/129815/ASUSWRT-3.0.0.4.376_1071-LAN-Backdoor-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.