Security Resilience

CVE-2023-52533

Google Android 12.0 … 14.0

Published
08 April 2024
Modified
06 May 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0036 28th percentile
Risk Priority 46 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-52533 is a medium-severity Undefined Behavior for Input to API (CWE-475) vulnerability in Google Android. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In modem-ps-nas-ngmm, there is a possible undefined behavior due to incorrect error handling. This could lead to remote information disclosure no additional execution privileges needed

CWE(s)
CWE-475

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
attack.mitre.org →
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-52343Same product: Google Android
CVE-2023-52342Same product: Google Android
CVE-2023-52344Same product: Google Android
CVE-2023-52341Same product: Google Android
CVE-2023-52534Same product: Google Android
CVE-2023-33914Same product: Google Android
CVE-2023-33915Same product: Google Android
CVE-2023-33913Same product: Google Android
CVE-2023-42726Same product: Google Android
CVE-2023-42725Same product: Google Android

Affected Assets

google
android
12.0, 13.0, 14.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover calls that supply invalid control-parameter values before deployment.

SI-10 Information Input Validation good match

Validating inputs to API control parameters ensures only permitted values are supplied, structurally eliminating the source of undefined behavior.

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.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record this class of API-related weakness.

PR.PS-06 partial match
blocks

Secure SDLC practices (coding standards, reviews, testing) directly prevent undefined behavior from invalid API inputs.

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.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle includes API specification and validation that can prevent undefined behavior from invalid inputs.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows or SQL injection) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent the undefined-behavior weakness from arising or being exploitable.

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

A.8.27 establishes and applies secure engineering principles (including least privilege, security by design, and distrusting external input) during architecture and development, but does not stop an already-written API from exhibiting undefined behavior on non-specific input values; the weakness remains present and exploitable.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses avoiding undefined behavior by enforcing defined inputs and error handling in APIs.

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

Security testing can detect undefined behavior from invalid API inputs before deployment.

References