Security Resilience

CVE-2024-43090

Access Control in Google Android 12.0 … 14.0

Published
13 November 2024
Modified
26 August 2025
CVSS Score v3.1 5.0
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:N/A:N
EPSS Score 0.0016 6th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-43090 is a medium-severity Missing Authorization (CWE-862) vulnerability in Google Android. Its CVSS base score is 5.0 (Medium).

Operationally, ranked at the 6th 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 AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In multiple locations, there is a possible cross-user image read due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is needed for exploitation.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-21244Same product: Google Android
CVE-2023-21388Same product: Google Android
CVE-2024-0038Same product: Google Android
CVE-2024-43087Same product: Google Android
CVE-2023-21123Same product: Google Android
CVE-2024-31332Same product: Google Android
CVE-2023-21173Same product: Google Android
CVE-2023-21002Same product: Google Android
CVE-2023-21122Same product: Google Android
CVE-2023-21393Same product: Google Android

Affected Assets

google
android
12.0, 12.1, 13.0, 14.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

AC-3 directly requires enforcement of authorization decisions on every access request, structurally eliminating missing authorization checks.

AC-24 mandates that access control decisions are applied to each request, preventing bypass of authorization logic.

AC-25 requires a tamperproof, always-invoked reference monitor that ensures authorization checks cannot be omitted.

AC-6 reduces the set of actions reachable without proper authorization, limiting blast radius of missing checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

A.8.3's purpose is to ensure only authorized access, and its guidance directly mandates the authorization checks that CWE-862 describes as missing, so a well-implemented access restriction control fully blocks exploitation of the missing authorization weakness.

finds

By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.

blocks

Requiring evidence of minimum security capabilities and acceptance testing ensures that missing or bypassed authorization checks are detected before the delivered software is accepted.

finds

Mandating read-only access or proxy execution by an authorized administrator ensures every requested operation is explicitly authorized before it occurs.

blocks

Mandatory authorization checks before allowing modifications ensure that every sensitive action on source code is preceded by an explicit access-control decision.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-862, a class-level weakness, and none of its children carries one either.

References