ON Semiconductor Quantenna Wi-Fi Chipset up to 8.0.0.28 router_command.sh put_file_to_qtn argument injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ON Semiconductor Quantenna Wi-Fi Chipset up to 8.0.0.28. This affects an unknown function of the file router_command.sh. Performing a manipulation of the argument put_file_to_qtn results in argument injection. This vulnerability is cataloged as CVE-2025-32456. The attack must be initiated from a local position. There is no exploit available.
Details
A vulnerability was found in ON Semiconductor Quantenna Wi-Fi Chipset up to 8.0.0.28. It has been classified as critical. This affects some unknown functionality of the file router_command.sh. The manipulation of the argument put_file_to_qtn with an unknown input leads to a argument injection vulnerability. CWE is classifying the issue as CWE-88. 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Quantenna Wi-Fi chipset ships with a local control script, router_command.sh (in the put_file_to_qtn argument), 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.
The weakness was shared by Ricky Lawshae. The advisory is shared at takeonme.org. This vulnerability is uniquely identified as CVE-2025-32456 since 04/09/2025. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-17407). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 8.0.0.0
- 8.0.0.1
- 8.0.0.2
- 8.0.0.3
- 8.0.0.4
- 8.0.0.5
- 8.0.0.6
- 8.0.0.7
- 8.0.0.8
- 8.0.0.9
- 8.0.0.10
- 8.0.0.11
- 8.0.0.12
- 8.0.0.13
- 8.0.0.14
- 8.0.0.15
- 8.0.0.16
- 8.0.0.17
- 8.0.0.18
- 8.0.0.19
- 8.0.0.20
- 8.0.0.21
- 8.0.0.22
- 8.0.0.23
- 8.0.0.24
- 8.0.0.25
- 8.0.0.26
- 8.0.0.27
- 8.0.0.28
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 7.7
CNA Vector (AHA): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Argument injectionCWE: CWE-88 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/09/2025 🔍06/09/2025 🔍
06/09/2025 🔍
01/14/2026 🔍
Sources
Advisory: takeonme.orgResearcher: Ricky Lawshae
Status: Not defined
CVE: CVE-2025-32456 (🔍)
GCVE (CVE): GCVE-0-2025-32456
GCVE (VulDB): GCVE-100-311649
EUVD: 🔍
Entry
Created: 06/09/2025 07:24Updated: 01/14/2026 00:58
Changes: 06/09/2025 07:24 (64), 06/09/2025 07:38 (1), 06/10/2025 09:18 (1), 01/14/2026 00:58 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.