CVE-2025-32459VulnerabilityPublished 8 Jun 2025Updated 10 Jun 2025

CVE-2025-32459: ON Semiconductor Quantenna Wi-Fi chipset · Argument Injection

Affects ON Semiconductor Quantenna Wi-Fi chipsetSource CVE Database V5

Not known to be exploited · CVSS 7.7 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ON Semiconductor Quantenna Wi-Fi chipset	Affected =0	Fixed in–

AI-suggested

Specific mitigation steps include: 1) Immediate audit of all devices using the Quantenna Wi-Fi chipset to identify affected versions. 2) Implement strict access controls to prevent unauthorized local access to devices, including physical security and network segmentation to limit administrative interface exposure. 3) Apply the vendor's best practice guidelines rigorously, which may include disabling or restricting the use of the vulnerable router_command.sh script or the sync_time argument. 4) Monitor device logs and network traffic for unusual command execution patterns or anomalies indicative of exploitation attempts. 5) Where possible, replace or upgrade devices to versions or alternative chipsets not affected by this vulnerability once patches or firmware updates become available. 6) Employ network-level protections such as intrusion detection/prevention systems (IDS/IPS) tuned to detect command injection patterns related to this vulnerability. 7) Educate IT and security teams about the vulnerability and the importance of minimizing local access vectors. These measures go beyond generic advice by focusing on access control, monitoring, and vendor-specific guidance implementation.

Description

The Quantenna Wi-Fi chipset ships with a local control script, router_command.sh (in the sync_time 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.

Impact

For European organizations, this vulnerability poses a significant risk, especially for enterprises and service providers relying on networking equipment or IoT devices powered by the Quantenna Wi-Fi chipset. Compromise of these devices can lead to unauthorized access to internal networks, interception or manipulation of sensitive data, and disruption of network services. Given the high confidentiality and integrity impact, attackers could exfiltrate sensitive corporate or personal data or alter device configurations to facilitate persistent access or lateral movement. The requirement for local access limits remote exploitation but does not eliminate risk, as attackers may leverage other vulnerabilities or social engineering to gain local access. The lack of a patch increases exposure, and the presence of best practice guidelines suggests mitigation is possible but requires proactive implementation. European organizations with extensive IoT deployments or managed network infrastructure should prioritize assessment and mitigation to prevent potential breaches that could affect business continuity, regulatory compliance (e.g., GDPR), and customer trust.

Summary

CVE-2025-32459 is a high-severity vulnerability (CVSS 7.7) affecting the ON Semiconductor Quantenna Wi-Fi chipset, specifically through a local control script named router_command.sh. The vulnerability is categorized under CWE-88, which involves improper neutralization of argument delimiters in commands, commonly referred to as 'argument injection' or command injection. In this case, the vulnerability exists in the handling of the 'sync_time' argument within the script. An attacker with local access to the device can exploit this flaw by injecting malicious command delimiters into the argument, causing arbitrary command execution with the privileges of the script. The CVSS vector indicates that the attack requires local access (AV:L), low attack complexity (AC:L), no privileges (PR:N), and no user interaction (UI:N), with unchanged scope (S:U). The impact on confidentiality and integrity is high (C:H/I:H), but availability is not affected (A:N). No known exploits have been reported in the wild yet. This vulnerability is critical for embedded devices using this chipset, such as routers and IoT devices, where local access can be achieved either physically or via other compromised vectors. Exploitation could lead to full compromise of the device's firmware or network functions, enabling attackers to manipulate network traffic, exfiltrate data, or pivot into internal networks.

CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Implementation · Parameterization
Where possible, avoid building a single string that contains the command and its arguments. Some languages or frameworks have functions that support specifying independent arguments, e.g. as an array, which is used to automatically perform the appropriate quoting or escaping while building the command.
Architecture and Design · Input Validation
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.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Flash Parameter Injection (opens in a new tab)
Using Meta-characters in E-mail Headers to Inject Malicious Payloads (opens in a new tab)
HTTP Parameter Pollution (HPP) (opens in a new tab)
OS Command Injection (opens in a new tab)
Parameter Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 01:27 UTC

WeaknessesCWE-88

Technical details

References

Community reviews

Related threats