Security Resilience

CVE-2010-5330

RCE in Ui Airos ≤ 4.0.1

CISA KEVActive ExploitationEUVD ExploitedPublic PoCRCECommand Injection
Published
11 June 2019
Modified
05 November 2025
KEV Added
15 April 2022
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.39 99th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2010-5330 is a critical-severity Command Injection (CWE-77) vulnerability in Ui Airos. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2010-5330 is a command injection vulnerability affecting certain Ubiquiti devices running Air OS, including the Nanostation5. The flaw resides in stainfo.cgi (Show AP info), where the ifname variable is not sanitized before being passed to a system command, allowing shell metacharacters in an unauthenticated GET request.

An attacker with network access can send a crafted HTTP GET request to the affected endpoint and execute arbitrary commands on the device. Successful exploitation grants full control over the device, enabling actions such as configuration changes, data exfiltration, or use of the device as a pivot point, consistent with the CVSS 9.8 rating and CWE-77 classification.

Ubiquiti community advisories and firmware release notes direct users to apply the fixed versions v4.0.1 for 802.11 ISP products, v5.3.5 for AirMax ISP products, or v5.4.5 for AirSync firmware to eliminate the injection vector.

The vulnerability appears in the CISA Known Exploited Vulnerabilities catalog and has publicly available exploit code on Exploit-DB, indicating confirmed real-world exploitation.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

AirMax ISP products, and v5.4.5 for AirSync firmware. For example, Nanostation5 (Air OS) is affected.

CWE(s)
KEV Date Added
15 April 2022

Related Threats

CVEs Like This One

CVE-2024-42025Same vendor: Ui
CVE-2026-21638Same vendor: Ui
CVE-2026-34908Same vendor: Uiboth on KEV
CVE-2023-1458Same vendor: Ui
CVE-2026-34910Same vendor: Uiboth on KEV
CVE-2023-38034Same vendor: Ui
CVE-2026-34909Same vendor: Uiboth on KEV
CVE-2023-1456Same vendor: Ui
CVE-2023-1457Same vendor: Ui
CVE-2007-3010Shared CWE-77both on KEV

Affected Assets

ui
airos
≤ 4.0.1 · 4.0.2 — 5.3.5 · 5.3.6 — 5.4.5

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References