Cyber Resilience

CVE-2024-20836

Memory Safety in Samsung Android 11.0 … 14.0

Published
05 March 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0016 5th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2024-20836 is a low-severity Out-of-bounds Read (CWE-125) vulnerability in Samsung Android. Its CVSS base score is 3.3 (Low).

Operationally, ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Out of bounds Read vulnerability in ssmis_get_frm in libsubextractor.so prior to SMR Mar-2024 Release 1 allows local attackers to read out of bounds memory.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-21054Same product: Samsung Android
CVE-2025-21055Same product: Samsung Android
CVE-2026-20973Same product: Samsung Android
CVE-2025-20887Same product: Samsung Android
CVE-2021-25487Same product: Samsung Android
CVE-2024-20882Same product: Samsung Android
CVE-2024-20820Same product: Samsung Android
CVE-2025-58479Same product: Samsung Android
CVE-2025-20944Same product: Samsung Android
CVE-2023-21477Same product: Samsung Android

Affected Assets

samsung
android
11.0, 12.0, 13.0, 14.0

Mitigating Controls

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-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

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.

detects

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
detects

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References