Cyber Resilience

CVE-2023-21193

Memory Safety in Google Android 13.0

Memory Safety
Published
28 June 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0044 37th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2023-21193 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Google Android. Its CVSS base score is 7.5 (High).

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

EU & UK References

Vulnerability Data

In VideoFrame of VideoFrame.h, there is a possible abort due to an integer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-233006499

CWE(s)
CWE-190

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.
attack.mitre.org →
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.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-0031Same product: Google Android
CVE-2024-31333Same product: Google Android
CVE-2026-0052Same product: Google Android
CVE-2025-48595Same product: Google Android
CVE-2023-48409Same product: Google Android
CVE-2026-0080Same product: Google Android
CVE-2026-0041Same product: Google Android
CVE-2026-0044Same product: Google Android
CVE-2026-0028Same product: Google Android
CVE-2026-0040Same product: Google Android

Affected Assets

google
android
13.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

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 use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect integer overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

A.8.26 Application security requirements partial match
degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References