dbcve.org
Qcs Ax3 S5 FirmwareOperating system · Onsemi

CVE-2025-32457

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 get_file_from_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

A command injection vulnerability exists in the Quantenna Wi-Fi chipset SDK's local control script router_command.sh within the get_file_from_qtn argument. The script improperly handles input, allowing argument injection (CWE-88). An attacker with local access can inject arbitrary commands, achieving high confidentiality and integrity impact despite no availability impact.

MitigationSince no vendor patch exists, implement input validation and sanitization on the router_command.sh script's arguments, disable or restrict the affected get_file_from_qtn functionality if not required, and follow Quantenna's published best practices guide for secure implementation.

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. Locate router_command.sh script
    Search the filesystem for the file router_command.sh, typically found in Quantenna SDK or firmware image at paths such as /etc/scripts/, /usr/bin/, or within the firmware squashfs root. Use: find / -name 'router_command.sh' 2>/dev/null
    Affected if The script exists on the system, indicating the Quantenna Wi-Fi chipset SDK is present
  2. Verify get_file_from_qtn argument handling
    Examine the router_command.sh script content and locate the get_file_from_qtn function or argument handler. Search for the string 'get_file_from_qtn' within the script using grep or by viewing the file directly
    Affected if The script contains a get_file_from_qtn argument handler without proper input sanitization on that parameter
  3. Check script accessibility and execution context
    Determine if the router_command.sh script is executable and accessible to local users. Check file permissions with ls -la on the script path. Identify if it can be invoked by unprivileged users or through any web/API interface
    Affected if The script is executable by the user context being assessed, allowing command injection through the get_file_from_qtn argument
  4. Confirm Quantenna firmware variant
    Identify the specific firmware model by checking /etc/version, /proc/version, or boot logs for the Onsemi product name (Qcs Ax3 S5, Qcs Ax2 A12/T12/T8, Qd840, Qhs710, Qsr10ga, or Qsr10gu)
    Affected if The device runs any of the listed Quantenna/Onsemi firmware variants, as all versions are affected

A user is affected if their device runs any of the listed Onsemi Quantenna firmware variants and contains the router_command.sh script with the vulnerable get_file_from_qtn argument accessible to local users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since no vendor patch exists, implement input validation and sanitization on the router_command.sh script's arguments, disable or restrict the affected get_file_from_qtn functionality if not required, and follow Quantenna's published best practices guide for secure implementation.

Recommended fix High confidence
  1. This vulnerability remains unpatched by the vendor as of this CVE's publication date.
  2. The vendor (Quantenna) has only released a best practices guide for implementors, not a security patch.
  3. Monitor vendor security advisories for future firmware updates that address CWE-88 in the router_command.sh script.
  4. As a mitigation, restrict physical and local access to devices using this chipset since the attack vector is local (AV:L).
  5. If possible, implement input validation or wrapper scripts around the get_file_from_qtn argument to prevent argument injection.
  6. Consider network segmentation to limit exposure if local access cannot be fully restricted.
Caveat No patched firmware version is available from the vendor at this time. The vendor has not released a security update; only a best practices guidance document exists.

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32457 — 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-32457 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