CVE-2022-25719
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 · uneditedInformation disclosure in WLAN due to improper length check while processing 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 buffer read overflow vulnerability exists in the WLAN firmware of Qualcomm Snapdragon chipsets. Due to an improper length check when processing the authentication handshake, an attacker within wireless range can potentially disclose sensitive information from the device's memory. The vulnerability affects multiple Snapdragon product lines used in mobile devices, IoT devices, wearables, automotive, and infrastructure equipment.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 chipset modelCheck the device's processor/system-on-chip identifier. On Linux systems, run 'cat /proc/cpuinfo' or check '/sys/devices/soc0/soc_id'. On Android, check 'Settings > About Phone > Model' or use 'lshw' or 'dmidecode' if available. For network devices, consult the hardware documentation or management interface.Affected if The chipset model matches any of: Apq8009, Apq8009w, Apq8016, Apq8017, Apq8037, Apq8052, or Apq8053.
-
Confirm WLAN firmware component is presentVerify that the device has WLAN (Wi-Fi) hardware and firmware capability. On Linux, check for wireless interfaces with 'ip link show' or 'iwconfig'. Check for WLAN firmware files in /lib/firmware or similar directories. On embedded devices, check the boot logs or system information for WLAN initialization messages.Affected if WLAN hardware and firmware are present and loaded on the device.
-
Check WLAN firmware versionQuery the WLAN firmware version if exposed. On Linux, use 'cat /sys/class/net/wlan*/device/firmware_version' or 'ethtool -i wlan0'. Some devices expose version via 'iw list' or vendor-specific tools. Consult device vendor documentation for firmware version retrieval.Affected if The installed firmware version corresponds to one of the affected chipset models listed.
-
Verify device has wireless exposureDetermine if the device is configured to accept wireless connections or is within range of potential attackers. Check if WLAN is enabled via 'nmcli device show' or similar network management tools. For infrastructure devices, verify the device's physical wireless accessibility.Affected if WLAN is enabled and the device is within wireless range of untrusted actors, making it susceptible to the authentication handshake attack vector.
The device is affected if it contains any of the listed Qualcomm APQ chipset models (Apq8009, Apq8009w, Apq8016, Apq8017, Apq8037, Apq8052, or Apq8053) with WLAN functionality enabled, as all firmware versions for these models are vulnerable.
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 · scopedApply vendor-supplied firmware updates for affected Snapdragon chipsets. As this is a WLAN firmware issue, priority should be given to devices with direct wireless exposure. Organizations should inventory affected hardware and coordinate with device manufacturers for patch deployment.
Firmware update from device manufacturer incorporating Qualcomm fix (specific version not provided in source material)
- Identify the specific device model that contains the affected Qualcomm APQ chipset (Apq8009, Apq8009w, Apq8016, Apq8017, Apq8037, Apq8052, Apq8053, or Apq8056)
- Contact the device manufacturer (OEM/ODM) to obtain firmware updates that address the WLAN out-of-bounds read vulnerability (CVE-2022-25719)
- Apply the manufacturer-provided firmware update to remediate the improper length check vulnerability in the WLAN authentication handshake processing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25719 — 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-25719 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