LiveActive security incident?Get immediate response
CVE Record

CVE-2022-25708: Memory corruption in WLAN due to buffer copy without checking size of input while parsing keys in Snapdrago...

Memory corruption in WLAN due to buffer copy without checking size of input while parsing keys in Snapdragon Connectivity, Snapdragon Mobile

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical Qualcomm WLAN memory-corruption flaw in affected Snapdragon mobile and connectivity components. The source data rates it 9.8 because the CVSS vector indicates network reachability, low complexity, no privileges, and no user interaction. Business risk is highest for fleets using devices built on the listed Snapdragon chipsets or wireless components.

Executive priority

Treat as high-priority exposure management for affected device fleets. The issue is critical by CVSS and sits in wireless connectivity code, but the provided sources do not prove active exploitation.

Technical view

CVE-2022-25708 is a CWE-120 buffer-copy issue in WLAN key parsing. The described failure is copying input without checking size, causing memory corruption. Affected Qualcomm components include Snapdragon Connectivity and Snapdragon Mobile parts such as SD 8 Gen1 5G, SD888 5G, SM7450, and listed WCN/WCD/WSA components.

Likely exposure

Exposure depends on whether owned or managed mobile, embedded, or wireless-enabled devices contain the listed Qualcomm Snapdragon components and have received the relevant vendor or OEM security update.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector still indicates a serious unauthenticated network attack surface with high confidentiality, integrity, and availability impact if exploitable.

Researcher notes

The public bundle provides affected component names, CWE-120 classification, and CVSS 3.1 vector. It does not provide exploit details, patch package identifiers, or device-model mappings, so validation must rely on Qualcomm and downstream OEM advisories.

Mitigation direction

  • Check Qualcomm's September 2022 bulletin for vendor guidance on CVE-2022-25708.
  • Identify OEM advisories for devices using the listed Snapdragon components.
  • Apply applicable OEM firmware or security updates when confirmed available.
  • Prioritize managed mobile and embedded assets with affected Qualcomm WLAN components.
  • Track unsupported or unpatched devices as risk exceptions.

Validation and detection

  • Inventory devices for the listed Snapdragon SoCs and WLAN components.
  • Map each device model to its OEM security bulletin or firmware notes.
  • Confirm installed firmware or security patch level addresses CVE-2022-25708.
  • Review MDM, EDR, or asset data for unpatched affected devices.
  • Document devices where component details cannot be confirmed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-25708 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-25708Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Connectivity, Snapdragon MobileSD 8 Gen1 5G, SD888 5G, SM7450, WCD9370, WCD9375, WCD9380, WCD9385, WCN6750, WCN6850, WCN6851, WCN6855, WCN6856, WCN7850, WCN7851, WSA8830, WSA8832, WSA8835Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.