CVE-2025-32455
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 · uneditedThe Quantenna Wi-Fi chipset ships with a local control script, router_command.sh (in the run_cmd 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 confidenceThe Quantenna Wi-Fi chipset includes a local control script (router_command.sh) that accepts a run_cmd argument vulnerable to argument injection (CWE-88). The script does not properly sanitize input before passing it to system commands, allowing a local attacker to inject arbitrary commands with the privileges of the script execution context.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Quantenna firmware variantExamine system firmware information, boot logs, or chipset identification to determine if the device runs Onsemi Quantenna firmware. Look for model identifiers such as Qcs Ax3 S5, Qcs Ax2 A12, Qcs Ax2 T12, Qcs Ax2 T8, Qd840, Qhs710, Qsr10ga, or Qsr10guAffected if The device runs any of the listed Quantenna firmware variants
-
Locate router_command.sh scriptSearch for the script file in the firmware filesystem. Common paths include /etc/, /usr/bin/, /sbin/, or /etc/scripts/. Use 'find / -name router_command.sh 2>/dev/null' or inspect firmware image if accessibleAffected if The router_command.sh script is present on the system
-
Verify run_cmd parameter acceptanceExamine the script contents using 'cat <path_to_script>' or decompile firmware to inspect the script code. Look for how the run_cmd argument is processed and whether it is passed to system commandsAffected if The script accepts and processes a run_cmd argument without sanitization
-
Confirm lack of input validationReview the script code for any input validation, escaping, or sanitization functions applied to the run_cmd parameter before it is used in command execution (e.g., passed to system(), exec(), or shell invocation)Affected if No input validation is performed on run_cmd before command execution
A system is affected if it runs any of the listed Quantenna firmware variants and contains the router_command.sh script that accepts an unsanitized run_cmd argument for command execution
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement input validation and sanitization on the run_cmd argument before passing to system calls, or contact Quantenna for firmware updates; apply compensating controls such as least-privilege execution and restricting local access until patch is available.
- This vulnerability is currently unpatched by the vendor.
- No firmware upgrade or patch is available at the time of this CVE publication.
- The vendor (Quantenna/onsemi) has only released a best practices guide for implementors of this chipset.
- Monitor vendor security advisories for future updates.
- Consider network segmentation to limit exposure if this service is accessible.
- Review the vendor's best practices guide at community.onsemi.com or takeonme.org for mitigation recommendations.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32455 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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