cve.bz

CVE-2023-21644 qualcomm: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.8 highEPSS 0.1%

High (7.8) in qualcomm. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Memory corruption in RIL due to Integer Overflow while triggering qcril_uim_request_apdu request.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-09-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-680 Integer Overflow to Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-21644 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-21644?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-21644?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-21644 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Qualcomm, Inc. SnapdragonAQT1000
Qualcomm, Inc. SnapdragonQCA6390
Qualcomm, Inc. SnapdragonQCA6391
Qualcomm, Inc. SnapdragonQCA6420
Qualcomm, Inc. SnapdragonQCA6426
Qualcomm, Inc. SnapdragonQCA6430
Qualcomm, Inc. SnapdragonQCA6436
Qualcomm, Inc. SnapdragonQCA6564
Qualcomm, Inc. SnapdragonQCA6564AU
Qualcomm, Inc. SnapdragonQCA6574A
Qualcomm, Inc. SnapdragonQCA6574AU
Qualcomm, Inc. SnapdragonQCA6595AU
Qualcomm, Inc. SnapdragonQCA6696
Qualcomm, Inc. SnapdragonQCC5100
Qualcomm, Inc. SnapdragonSA515M
Qualcomm, Inc. SnapdragonSA6145P
Qualcomm, Inc. SnapdragonSA6150P
Qualcomm, Inc. SnapdragonSA6155P
Qualcomm, Inc. SnapdragonSA8145P
Qualcomm, Inc. SnapdragonSA8150P
Qualcomm, Inc. SnapdragonSA8155P
Qualcomm, Inc. SnapdragonSA8195P
Qualcomm, Inc. SnapdragonSD855
Qualcomm, Inc. SnapdragonSD865 5G
Qualcomm, Inc. SnapdragonSD870
Qualcomm, Inc. SnapdragonSDA429W
Qualcomm, Inc. SnapdragonSDX55
Qualcomm, Inc. SnapdragonSDX55M
Qualcomm, Inc. SnapdragonSDXR2 5G
Qualcomm, Inc. SnapdragonSW5100
Qualcomm, Inc. SnapdragonSW5100P
Qualcomm, Inc. SnapdragonWCD9341
Qualcomm, Inc. SnapdragonWCD9360
Qualcomm, Inc. SnapdragonWCD9380
Qualcomm, Inc. SnapdragonWCN3610
Qualcomm, Inc. SnapdragonWCN3660B
Qualcomm, Inc. SnapdragonWCN3680B
Qualcomm, Inc. SnapdragonWCN3980
Qualcomm, Inc. SnapdragonWCN3988
Qualcomm, Inc. SnapdragonWCN3998
Qualcomm, Inc. SnapdragonWCN6850
Qualcomm, Inc. SnapdragonWCN6851
Qualcomm, Inc. SnapdragonWSA8810
Qualcomm, Inc. SnapdragonWSA8815
Qualcomm, Inc. SnapdragonWSA8830
Qualcomm, Inc. SnapdragonWSA8835

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-680 (11).

References

Check your stackJSON