Authenticated server crash via duplicate MSETNX key
Published Mar 20, 2023 · Updated Feb 25, 2025
Denial of service in Redis 7.0.8 through 7.0.9 allows remote authenticated users to terminate the server via a crafted MSETNX command. In msetGenericCommand, repeating a nonexistent key causes setKey to receive SETKEY_DOESNT_EXIST on the second write, violating an assertion. The command must be authorized, and successful exploitation terminates the Redis process rather than exposing or modifying data.
Summary
What happened
Denial of service in Redis 7.0.8 through 7.0.9 allows remote authenticated users to terminate the server via a crafted MSETNX command. In msetGenericCommand, repeating a nonexistent key causes setKey to receive SETKEY_DOESNT_EXIST on the second write, violating an assertion. The command must be authorized, and successful exploitation terminates the Redis process rather than exposing or modifying data.
The record
- CVE
- CVE-2023-28425
- Published
- Mar 20, 2023
- Updated
- Feb 25, 2025
- Vendor
- Redis
- Product
- Redis
- Classifications
- CWE-77, CWE-617, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 7.0.8, < 7.0.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo