Cyber Resilience

CVE-2023-28565

Memory Safety in Qualcomm Snapdragon 820 Firmware

Published
05 September 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0011 1th percentile
Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2023-28565 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Qualcomm Snapdragon 820 Firmware. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Memory corruption in WLAN HAL while handling command streams through WMI interfaces.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-28567Same product: Qualcomm Aqt1000
CVE-2023-28564Same product: Qualcomm Aqt1000
CVE-2023-28573Same product: Qualcomm Aqt1000
CVE-2023-28558Same product: Qualcomm Aqt1000
CVE-2023-28560Same product: Qualcomm Apq8076
CVE-2023-21628Same product: Qualcomm Apq8017
CVE-2023-28559Same product: Qualcomm Aqt1000
CVE-2023-21650Same product: Qualcomm Aqt1000
CVE-2023-24851Same product: Qualcomm Ar8035
CVE-2023-22386Same product: Qualcomm Ar8035

Affected Assets

qualcomm
9205 lte firmware
all versions
qualcomm
apq8017 firmware
all versions
qualcomm
apq8064au firmware
all versions
qualcomm
apq8076 firmware
all versions
qualcomm
apq8092 firmware
all versions
qualcomm
apq8094 firmware
all versions
qualcomm
aqt1000 firmware
all versions
qualcomm
ar7420 firmware
all versions
qualcomm
ar8031 firmware
all versions
qualcomm
ar8035 firmware
all versions
+284 more product configuration(s) — see NVD for full list

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-787

Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.

prevents

Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.

prevents

Application security requirements include validation of untrusted input used for indexing or addressing memory structures.

prevents

Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.

prevents

Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References