Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-28425 is a medium-severity Command Injection (CWE-77) vulnerability in Redis Redis. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 1% 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-28425 affects Redis, an in-memory database that persists on disk. Starting in version 7.0.8 and prior to 7.0.10, authenticated users can invoke the MSETNX command to trigger a runtime assertion that terminates the server process. The flaw is tracked under CWE-77 and CWE-617 and carries a CVSS 3.1 score of 5.5 reflecting local attack vector, low complexity, and high availability impact.
An attacker who already possesses a valid Redis account on the affected host can execute the MSETNX command to crash the server, resulting in a denial-of-service condition. No additional user interaction or elevated privileges beyond a standard authenticated session are required.
The official fix is included in Redis 7.0.10. The project advisory and commit reference 48e0d4788434833b47892fe9f3d91be7687f25c9 document the patch, while NetApp’s advisory NTAP-20230413-0005 lists affected products and remediation guidance. The EPSS score has remained at 0.4529 with no material increase after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-32121
Vulnerability Data
Redis is an in-memory database that persists on disk. Starting in version 7.0.8 and prior to version 7.0.10, authenticated users can use the MSETNX command to trigger a runtime assertion and termination of the Redis server process. The problem is…
more
fixed in Redis version 7.0.10.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
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 require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
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 require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.