Quantenna Wi-Fi chipset: Improper Neutralization of Argument Delimiters in a Command
CVE-2025-3460 is a high-severity improper neutralization of argument delimiters in a command vulnerability in Quantenna Wi-Fi chipset from ON Semiconductor, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Quantenna Wi-Fi chipset versions: 8.0.0.28 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1% chance of exploitation within 30 days, higher than 63% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Quantenna Wi-Fi chipset you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ON Semiconductor | Quantenna Wi-Fi chipset | 8.0.0.28 and earlier | Not stated |
| Onsemi | Qcs-ax3-s5 Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax2-a12 Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax2-t12 Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax2-t8 Firmware | Not specified in the record | Not stated |
| Onsemi | Qd840 Firmware | Not specified in the record | Not stated |
| Onsemi | Qhs710 Firmware | Not specified in the record | Not stated |
| Onsemi | Qsr10ga Firmware | Not specified in the record | Not stated |
| Onsemi | Qsr10gu Firmware | Not specified in the record | Not stated |
| Onsemi | Qv840 Firmware | Not specified in the record | Not stated |
| Onsemi | Qv840c Firmware | Not specified in the record | Not stated |
| Onsemi | Qv860 Firmware | Not specified in the record | Not stated |
| Onsemi | Qv940 Firmware | Not specified in the record | Not stated |
| Onsemi | Qv942c Firmware | Not specified in the record | Not stated |
| Onsemi | Qv952c Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax2-s5 Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax3-a12 Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax3-t12 Firmware | Not specified in the record | Not stated |
| Onsemi | Qcs-ax3-t8 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.7 | High | CNA (takeonme.org) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
The Quantenna Wi-Fi chipset ships with a local control script, set_tx_pow, that is vulnerable to command injection. This is an instance of CWE-88, "Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')," and is estimated as a CVSS 7.7 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). This issue affects Quantenna Wi-Fi chipset through version 8.0.0.28 of the latest SDK, and appears to be unpatched at the time of this CVE record's first publishing, though the vendor has released a best practices guide for implementors of this chipset.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Argument Delimiters in a Command
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
How developers prevent this class of flaw
- Understand all the potential areas where untrusted inputs can enter your product: parameters or arguments, cookies, anything read from the network, environment variables, request headers as well as content, URL components, e-mail, files, databases, and any external systems that provide data to the application. Perform input validation at well-defined interfaces.
- Directly convert your input type into the expected data type, such as using a conversion function that translates a string into a number. After converting to the expected data type, ensure that the input's values fall within the expected range of allowable values and that multi-field consistencies are maintained.
- When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
More Improper Neutralization of Argument Delimiters in a Command vulnerabilities (CWE-88)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Technical write-ups (may include proof of concept)
- takeonme.org/cves/cve-2025-3460Exploit, Third Party Advisory
Other vulnerabilities in Quantenna Wi-Fi chipset
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Improper Neutralization of Argument Delimiters in a Command vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.