Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-36824 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Fedoraproject Fedora. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.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.
Redis 7.0 prior to version 7.0.12 contains a heap overflow vulnerability in the logic that extracts key names from commands and argument lists. The flaw can be triggered by the COMMAND GETKEYS and COMMAND GETKEYSANDFLAGS subcommands or by any command whose key names are matched by ACL rules, resulting in out-of-bounds reads, heap corruption, and potential remote code execution. The issue is tracked under CWE-122, CWE-131, and CWE-787 and carries a CVSS 3.1 score of 7.4.
Authenticated users are able to exploit the condition by submitting specially crafted commands that reference variadic key-name lists. Successful exploitation can disclose heap memory contents or corrupt allocator state, enabling arbitrary code execution on the Redis server process.
The vulnerability is fixed in Redis 7.0.12. The official advisory and release notes recommend immediate upgrade; downstream distributions such as Fedora have published corresponding package updates, and NetApp has issued an advisory for affected storage products. The EPSS score has remained near its peak of 0.9084 with a current value of 0.8900.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-40750
Vulnerability Data
Redis is an in-memory database that persists on disk. In Redit 7.0 prior to 7.0.12, extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap…
more
memory, heap corruption and potentially remote code execution. Several scenarios that may lead to authenticated users executing a specially crafted `COMMAND GETKEYS` or `COMMAND GETKEYSANDFLAGS`and authenticated users who were set with ACL rules that match key names, executing a specially crafted command that refers to a variadic list of key names. The vulnerability is patched in Redis 7.0.12.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
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.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
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.
Secure coding standards directly require correct buffer-size calculations.
Security testing in development and acceptance can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Change management can enforce review gates that catch unsafe memory operations before deployment.