We have recently released new version of AirMax AirOS firmware v6.3.0 for TI, XW and XM boards that fixes vulnerabilities found on AirMax AirOS v6.2.0 and prior TI, XW and XM boards, according to the description below:There are certain end-points containing functionalities that are vulnerable to command injection. It is possible to craft an input string that passes the filter check but still contains commands, resulting in remote code execution.Mitigation:Update to the latest AirMax AirOS firmware version available at the AirMax download page.
This vulnerability carries a CRITICAL severity rating with a CVSS v3.1 score of 9.8, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 51 products from ui, from ui, from ui and 48 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2020, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2020-05-26T16:15:12.867
2024-11-21T05:38:25.893
Modified
CVSSv3.1: 9.8 (CRITICAL)
AV:N/AC:L/Au:N/C:P/I:P/A:P
10.0
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | ui | airos | ≤ 6.2.0 | Yes |
| Hardware | ui | ag-hp-2g16 | - | No |
| Hardware | ui | ag-hp-2g20 | - | No |
| Hardware | ui | ag-hp-5g23 | - | No |
| Hardware | ui | ag-hp-5g27 | - | No |
| Hardware | ui | airgrid_m | - | No |
| Hardware | ui | airgrid_m2 | - | No |
| Hardware | ui | airgrid_m5 | - | No |
| Hardware | ui | ar | - | No |
| Hardware | ui | ar-hp | - | No |
| Hardware | ui | bm2-ti | - | No |
| Hardware | ui | bm2hp | - | No |
| Hardware | ui | bm5-ti | - | No |
| Hardware | ui | bm5hp | - | No |
| Hardware | ui | is-m5 | - | No |
| Hardware | ui | lbem5-23 | - | No |
| Hardware | ui | litestation_m5 | - | No |
| Hardware | ui | locom2 | - | No |
| Hardware | ui | locom5 | - | No |
| Hardware | ui | locom9 | - | No |
| Hardware | ui | m2 | - | No |
| Hardware | ui | m3 | - | No |
| Hardware | ui | m365 | - | No |
| Hardware | ui | m5 | - | No |
| Hardware | ui | m900 | - | No |
| Hardware | ui | nb-2g18 | - | No |
| Hardware | ui | nb-5g22 | - | No |
| Hardware | ui | nb-5g25 | - | No |
| Hardware | ui | nbe-m2-13 | - | No |
| Hardware | ui | nbe-m5-16 | - | No |
| Hardware | ui | nbe-m5-19 | - | No |
| Hardware | ui | nbm3 | - | No |
| Hardware | ui | nbm365 | - | No |
| Hardware | ui | nbm9 | - | No |
| Hardware | ui | nsm2 | - | No |
| Hardware | ui | nsm3 | - | No |
| Hardware | ui | nsm365 | - | No |
| Hardware | ui | nsm5 | - | No |
| Hardware | ui | pbe-m2-400 | - | No |
| Hardware | ui | pbe-m5-300 | - | No |
| Hardware | ui | pbe-m5-300-iso | - | No |
| Hardware | ui | pbe-m5-400 | - | No |
| Hardware | ui | pbe-m5-400-iso | - | No |
| Hardware | ui | pbe-m5-620 | - | No |
| Hardware | ui | pbm10 | - | No |
| Hardware | ui | pbm365 | - | No |
| Hardware | ui | pbm5 | - | No |
| Hardware | ui | picom2hp | - | No |
| Hardware | ui | power_ap_n | - | No |
| Hardware | ui | rm2-ti | - | No |
| Hardware | ui | rm5-ti | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For ui's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.