Cyber 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

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, 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

CVEs Like This One

CVE-2023-52343Same product: Google Android
CVE-2023-52344Same product: Google Android
CVE-2023-52534Same product: Google Android
CVE-2023-52342Same product: Google Android
CVE-2023-33914Same product: Google Android
CVE-2023-33915Same product: Google Android
CVE-2023-52341Same product: Google Android
CVE-2023-33913Same product: Google Android
CVE-2023-42724Same product: Google Android
CVE-2023-42727Same 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.

PR.PS-06 mostly match
prevents

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

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record this class of API-related 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.

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

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

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate explicit input validation and defined behavior for API parameters.

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

Secure system architecture principles can require defensive coding that eliminates undefined behavior in APIs.

A.8.28 Secure coding partial match
prevents

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

References