CVE-2022-25718
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 issue in WLAN due to improper check on return value while authentication handshake in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
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 authentication handshake implementation where return values from cryptographic operations are not properly checked. This improper validation during the authentication process could allow an attacker to bypass security controls or manipulate the cryptographic handshake, potentially leading to authentication bypass or man-in-the-middle attacks.
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 device chipset modelCheck the device hardware specifications, system information, or bootloader output to determine the chipset model. On Linux systems, this may be available via 'lshw', 'dmidecode', or /proc/cpuinfo. On embedded devices, check the SoC documentation or boot logs.Affected if The chipset matches any of the following: Apq8009, Apq8009w, Apq8016, Apq8017, Apq8037, Apq8052, or Apq8053.
-
Confirm chipset is a Qualcomm APQ variantVerify the chipset is specifically a Qualcomm APQ (Application Processor Qualcomm) processor, not a different Qualcomm Snapdragon variant.Affected if The chipset is one of the listed Qualcomm APQ variants.
-
Check if WLAN functionality is enabledInspect system network configuration, kernel modules, or device management interface to determine if wireless LAN (Wi-Fi) is actively enabled on the device.Affected if WLAN is enabled and the device can connect to wireless networks.
-
Verify WLAN authentication is in useReview WLAN configuration to confirm the device is configured to use WPA/WPA2/WPA3 or other authentication mechanisms during the handshake process.Affected if WLAN authentication (such as WPA3, WPA2-Enterprise, or WPA2-PSK) is configured and active.
A device is affected if it uses any of the listed Qualcomm APQ chipsets (Apq8009 through Apq8053) and has WLAN functionality enabled with active authentication.
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-provided firmware updates for affected Snapdragon chipsets. Until patches are available, restrict WLAN access to trusted networks and monitor for anomalous authentication behavior.
- 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-25718 — 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-25718 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