CVE-2022-25674
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 · uneditedCryptographic issues in WLAN during the group key handshake of the WPA/WPA2 protocol in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music
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 · moderate confidenceA cryptographic vulnerability exists in the WLAN component's implementation of the group key handshake for WPA/WPA2 protocol in affected Snapdragon IoT chipsets. The group key handshake is critical for establishing encryption keys for broadcast/multicast traffic, and flaws here could allow an attacker to inject or decrypt network traffic.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the Qualcomm chipset modelReview device documentation, hardware specifications, or use system commands such as 'lspci', 'lsusb', 'cat /proc/cpuinfo', or vendor-specific diagnostic tools to determine the exact chipset model (Ar8031, Csra6620, Csra6640, Mdm9205, Qca4004, Qca4010, Qca4020, or Qca4024)Affected if The chipset matches one of the eight affected models listed in the CVE (Ar8031, Csra6620, Csra6640, Mdm9205, Qca4004, Qca4010, Qca4020, or Qca4024)
-
Check the firmware versionUse vendor-specific commands or tools to query the WLAN firmware version (for example, 'at+qgetver' for Quectel modules, 'fw_printenv', or consult device management interfaces)Affected if The firmware version is any version, since all versions of the affected chipsets are vulnerable according to the CVE (all versions)
-
Verify WLAN functionality is enabledCheck if the WLAN interface is active by running commands like 'iwconfig', 'ip link show', or checking the device's network configuration settingsAffected if WLAN is enabled and the device is capable of wireless communication using the affected chipset
-
Confirm WPA/WPA2 security protocol is in useInspect the wireless network configuration to verify if WPA or WPA2 security protocols are enabled (check via 'iwlist', 'nmcli', router web interface, or device wireless settings)Affected if WPA or WPA2 encryption is configured on the wireless network, as the vulnerability specifically exists in the group key handshake for these protocols
A user is affected if they are using any of the eight listed Qualcomm IoT chipsets (Ar8031, Csra6620, Csra6640, Mdm9205, Qca4004, Qca4010, Qca4020, Qca4024) with WLAN enabled and WPA/WPA2 security configured.
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 dataApply vendor-supplied firmware updates for affected Snapdragon Consumer IOT, Industrial IOT, and Voice & Music devices. Until patches are available, consider network segmentation to limit exposure of vulnerable devices.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25674 — 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-2022-25674 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