CVE-2025-3459
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, transmit_file, 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 named 'transmit_file' that contains a command injection vulnerability (CWE-88 - Argument Injection). This is a locally exploitable flaw (AV:L) requiring no privileges or user interaction, allowing an attacker with local access to inject arbitrary commands through improper neutralization of argument delimiters, achieving high confidentiality and integrity impact.
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 Wi-Fi chipset presenceExamine the system for Quantenna Wi-Fi hardware or firmware. Check for the presence of Onsemi/Qualcomm Quantenna chipset identifiers in system logs, device information, or network configuration. Look for firmware images containing model identifiers such as Qcs Ax3 S5, Qcs Ax2 A12/T12/T8, Qd840, Qhs710, Qsr10ga, or Qsr10gu.Affected if The system runs any of the listed Quantenna firmware variants (Qcs Ax3 S5, Qcs Ax2 A12/T12/T8, Qd840, Qhs710, Qsr10ga, Qsr10gu)
-
Locate the transmit_file scriptSearch the filesystem for a script or binary named 'transmit_file'. On embedded devices, typical paths may include /bin/, /usr/bin/, /sbin/, /usr/sbin/, /etc/scripts/, or proprietary Quantenna directories. Use commands like 'find / -name transmit_file 2>/dev/null' or check known Quantenna configuration directories.Affected if The 'transmit_file' script exists on the system
-
Verify script accessibility for local usersCheck file permissions on the located 'transport_file' script using 'ls -la <path_to_script>'. Determine if unprivileged local users can read or execute the script. Also check ownership and group settings.Affected if The script is readable or executable by users with local access (permissions include world-readable or world-executable, or group-readable/executable for groups that local users belong to)
-
Confirm firmware is unpatchedReview any available firmware release notes or security patches from Onsemi/Quantenna. Since vendor advisories indicate this vulnerability remains unpatched, check if the installed firmware version matches any known patched release (none listed as patched in the CVE).Affected if The installed firmware version has not received a security patch addressing CVE-2025-3459 (no patch available as of the CVE disclosure)
A user is affected if their system contains any of the listed Quantenna firmware variants with the 'transmit_file' script accessible to local users, allowing command injection through argument injection.
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.
From vendor dataSince this vulnerability remains unpatched by the vendor, implementers should apply the vendor's released best practices guide, restrict physical and logical access to the chipset's local management interfaces, and consider network segmentation to limit exposure to local attackers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-3459 — 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-3459 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