dbcve.org
Qcs Ax3 S5 FirmwareOperating system · Onsemi

CVE-2025-32456

HIGH · 7.8 CVSS v3.1 Published 2025-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Quantenna Wi-Fi chipset ships with a local control script router_command.sh containing the put_file_to_qtn argument that is vulnerable to command injection (CWE-88). The script fails to properly neutralize argument delimiters, allowing a local attacker to inject and execute arbitrary commands through the vulnerable parameter.

MitigationSince the vendor has not released a patch, implementers should apply the vendor best practices guide: implement strict input validation on the put_file_to_qtn argument, avoid passing unvalidated user-controlled input to shell commands, and restrict execution permissions on the script.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qcs Ax3 S5 FirmwareOperating system
Affected:all versions
Qcs Ax2 A12 FirmwareOperating system
Affected:all versions
Qcs Ax2 T12 FirmwareOperating system
Affected:all versions
Qcs Ax2 T8 FirmwareOperating system
Affected:all versions
Qd840 FirmwareOperating system
Affected:all versions
Qhs710 FirmwareOperating system
Affected:all versions
Qsr10ga FirmwareOperating system
Affected:all versions
Qsr10gu FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Quantenna Wi-Fi chipset firmware
    Check system firmware version or Wi-Fi chipset model. Look for Onsemi QCS Ax3 S5, QCS Ax2 (A12, T12, T8), Qd840, Qhs710, Qsr10ga, or Qsr10gu firmware. Consult device documentation or check /proc/version, /etc/version, or UBI partition for firmware strings.
    Affected if The device runs any version of the listed Onsemi QCS firmware variants.
  2. Locate the router_command.sh script
    Search for the vulnerable script in common paths such as /usr/bin/, /bin/, /sbin/, /etc/scripts/, or the vendor-specific config directory. Use: find / -name 'router_command.sh' 2>/dev/null
    Affected if The router_command.sh script exists on the system, indicating Quantenna firmware is present.
  3. Verify script permissions and accessibility
    Check if the script has execute permissions and is accessible to the attacker context. Use: ls -la <path_to_router_command.sh>
    Affected if The script is executable (chmod +x) and readable by the attacking user context.
  4. Inspect put_file_to_qtn argument handling
    Examine the script content for the put_file_to_qtn parameter. Use: grep -n 'put_file_to_qtn' <path_to_router_command.sh> or cat <path_to_router_command.sh> to view the argument parsing logic.
    Affected if The script contains a put_file_to_qtn argument handler that passes input directly to shell commands without proper sanitization.
  5. Check for input validation on the vulnerable argument
    Review the code around put_file_to_qtn for validation functions (sed, awk, grep for sanitization patterns). Look for shell metacharacter filtering or use of 'eval', 'system()', or backticks with the argument.
    Affected if No input validation is present, or the script uses unvalidated user input in shell execution contexts (eval, backticks, $() substitution).

The system is affected if it runs any version of the listed Onsemi QCS firmware variants and contains the router_command.sh script with an accessible put_file_to_qtn argument that lacks input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not released a patch, implementers should apply the vendor best practices guide: implement strict input validation on the put_file_to_qtn argument, avoid passing unvalidated user-controlled input to shell commands, and restrict execution permissions on the script.

Fix this in Qcs Ax3 S5 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32456 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32456 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data