Security Resilience

CVE-2023-40077

Race Condition in Google Android 11.0 … 14.0

Published
04 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.084 95th percentile
Risk Priority 69 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-40077 is a high-severity Race Condition (CWE-362) vulnerability in Google Android. Its CVSS base score is 8.1 (High).

Operationally, ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-40077 is a use-after-free write vulnerability caused by a race condition in multiple functions within MetaDataBase.cpp of the Android frameworks/av media component. The flaw is tracked under CWE-362 and carries a CVSS 3.1 score of 8.1, reflecting network attackability with high complexity but no required privileges or user interaction.

An unauthenticated remote attacker can trigger the race condition to perform an arbitrary write, resulting in privilege escalation on the affected Android device. Exploitation requires no additional execution rights beyond network access to the vulnerable media-handling paths.

The December 2023 Android security bulletin and the referenced frameworks/av commit 58fd993a89a3a22fa5a4a1a4548125c6783ec80c address the issue through upstream patching; devices should be updated to the December 2023 or later monthly release that incorporates the fix. The associated EPSS score has remained flat at 0.1079 with no material post-disclosure increase.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In multiple functions of MetaDataBase.cpp, there is a possible UAF write due to a race condition. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-48577Same product: Google Android
CVE-2024-34732Same product: Google Android
CVE-2024-0041Same product: Google Android
CVE-2025-48568Same product: Google Android
CVE-2026-0083Same product: Google Android
CVE-2023-21262Same product: Google Android
CVE-2026-0068Same product: Google Android
CVE-2024-32908Same product: Google Android
CVE-2026-55318Same product: Google Android
CVE-2024-34731Same product: Google Android

Affected Assets

google
android
11.0, 12.0, 12.1, 13.0, 14.0

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-362

Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.

addresses: CWE-362

Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

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.

blocks

A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing including code scans/penetration tests, developer training) that reach race conditions in concurrent code, but only as one slice of a broad requirement whose implementation scope and rigour are left to the organisation.

blocks

A.8.26 explicitly lists resilience against malicious attacks including SQL injections and input validation as application security requirements to identify/address; race conditions are a similar class of timing-based concurrency flaw that can be mitigated by requirements for proper synchronization/locking, but this is only one slice of the broad CWE-362 class (most instances arise in low-level shared-memory or TOCTOU scenarios not named here).

blocks

Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.

prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

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-362, a class-level weakness, and none of its children carries one either.

References