CVE-2010-5330
Ubiquiti AirOS Command Injection Vulnerability
Ubiquiti AirOS
On certain Ubiquiti devices, Command Injection exists via a GET request to stainfo.cgi (aka Show AP info) because the ifname variable is not sanitized, as demonstrated by shell metacharacters. The fixed version is v4.0.1 for 802.11 ISP products, v5.3.5 for AirMax ISP products, and v5.4.5 for AirSync firmware. For example, Nanostation5 (Air OS) is affected.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 15 April 2022. US federal agencies were required to remediate it by 6 May 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 40.2%, which is higher than 98.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2010-5330 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2010-5330.
What does CVE-2010-5330 affect?
CVE-2010-5330 affects Ubiquiti AirOS. On certain Ubiquiti devices, Command Injection exists via a GET request to stainfo.cgi (aka Show AP info) because the ifname variable is not sanitized, as demonstrated by shell metacharacters. The fixed version is v4.0.1 for 802.11 ISP products, v5.3.5 for AirMax ISP products, and v5.4.5 for AirSync firmware. For example, Nanostation5 (Air OS) is affected.
How severe is CVE-2010-5330?
CVE-2010-5330 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 40.2%, higher than 98.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 6 May 2022.
How should organisations respond to CVE-2010-5330?
Apply the vendor patch for Ubiquiti AirOS as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.