Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-20141 is a medium-severity Write-what-where Condition (CWE-123) vulnerability in Google Android. Its CVSS base score is 6.6 (Medium).
Operationally, ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17856
Vulnerability Data
In V5 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed.…
more
User interaction is needed for exploitation. Patch ID: ALPS09291402; Issue ID: MSV-2073.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
—
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.
Write-what-where primitives are neutralized when the attacker cannot execute the memory they control.
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.
Secure SDLC practices directly prevent arbitrary write conditions via safe coding, bounds checking, and memory-safe constructs.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding 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.
Security testing in development and acceptance can detect write-what-where conditions before deployment.
Secure development lifecycle practices directly reduce the likelihood of write-what-where flaws such as buffer overflows.
Application security requirements can mandate input validation and bounds checking that mitigate arbitrary write conditions.
Secure architecture and engineering principles discourage unsafe memory handling that leads to write-what-where vulnerabilities.
Secure coding standards explicitly forbid unsafe buffer operations that enable arbitrary memory writes.
Change management processes help ensure security fixes for such weaknesses are properly deployed.