Cyber Resilience

CVE-2024-31331

Google Android 12.0 … 14.0

Published
09 July 2024
Modified
14 March 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0012 2th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2024-31331 is a high-severity Operator Precedence Logic Error (CWE-783) vulnerability in Google Android. Its CVSS base score is 7.3 (High).

Operationally, ranked at the 2th 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 SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In setMimeGroup of PackageManagerService.java, there is a possible way to hide the service from Settings due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed…

more

for exploitation.

CWE(s)
NVD-CWE-noinfoCWE-783

Related Threats

CVEs Like This One

CVE-2024-31326Same product: Google Android
CVE-2024-34726Same product: Google Android
CVE-2024-34720Same product: Google Android
CVE-2024-34723Same product: Google Android
CVE-2024-31335Same product: Google Android
CVE-2024-32896Same product: Google Android
CVE-2024-34741Same product: Google Android
CVE-2025-48543Same product: Google Android
CVE-2025-36891Same product: Google Android
CVE-2023-40088Same product: Google Android

Affected Assets

google
android
12.0, 12.1, 13.0, 14.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis directly find incorrect evaluation results caused by precedence mistakes.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and coding rules can require constructs that eliminate ambiguous operator precedence.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate explicit parentheses and precedence rules that structurally prevent the logic error from being written.

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 (reviews, static analysis, testing) directly catch precedence errors while the control also addresses many other development risks.

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 logic errors caused by precedence issues.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes code review and testing that can catch precedence errors.

A.8.28 Secure coding partial match
prevents

Secure coding standards and guidelines directly address operator precedence mistakes.

References