CVE-2023-22458: Integer overflow in multiple Redis commands can lead to denial-of-service
Noroxi assessment
Priority: Plan (action score 44/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 71.9% (FIRST EPSS); higher than 99.4% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: redis (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-devel (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-doc (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5.
Add it to your regular patch cycle. Upgrade to redis (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-devel (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-doc (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Redis is an in-memory database that persists on disk. Authenticated users can issue a `HRANDFIELD` or `ZRANDMEMBER` command with specially crafted arguments to trigger a denial-of-service by crashing Redis with an assertion failure. This problem affects Redis versions 6.2 or newer up to but not including 6.2.9 as well as versions 7.0 up to but not including 7.0.8. Users are advised to upgrade. There are no known workarounds for this vulnerability.
- Published
- Jan 20, 2023
- Updated
- Jun 17, 2026
- EPSS
- 71.9% · 99th percentile
- CWE
- CWE-190
Report tools
Action score
44
Add it to your regular patch cycle.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 22 / 30 · 71.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · GitHub_M
- 5.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is Redis on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redis | redis | cpe:2.3:a:redis:redis |
Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)
Is Redis on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
redis redis
- >= 6.2, < 6.2.9, >= 7.0, < 7.0.8affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redis redis6.2.0 and later · before 6.2.9
- redis redis7.0.0 and later · before 7.0.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | redis | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:8 | redis-devel | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:8 | redis-doc | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| Alpine:v3.14 | redis | from 6.2.0 · before 6.2.9-r0 | 6.2.9-r0 |
| Alpine:v3.16 | redis | from 6.2.0 · before 7.0.8-r0 | 7.0.8-r0 |
| Debian:12 | redis | before 5:7.0.8-1 | 5:7.0.8-1 |
| openSUSE:Leap 15.4 | redis | before 6.2.6-150400.3.11.1 | 6.2.6-150400.3.11.1 |
| openSUSE:Tumbleweed | redis | before 7.0.8-1.1 | 7.0.8-1.1 |
| Red Hat:enterprise_linux:8::appstream | redis | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-debuginfo | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-debugsource | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-devel | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-doc | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Rocky Linux:8 | redis | before 0:6.2.17-1.module+el8.10.0+1923+5b85c6a7 | 0:6.2.17-1.module+el8.10.0+1923+5b85c6a7 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP4 | redis | before 6.2.6-150400.3.11.1 | 6.2.6-150400.3.11.1 |
Same product
redis: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox…KEV100Now
- CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution64This week
- CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis58Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-3734Oct 28, 2022 · Redis on Windows dbghelp.dll uncontrolled search path39Monitor
- ← EarlierCVE-2022-35977Jan 20, 2023 · Integer overflow in certain command arguments can drive Redis to OOM panic26Monitor
- Later →CVE-2022-36021Mar 1, 2023 · Redis string pattern matching can be abused to achieve Denial of Service40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:redis | 6.2.17-1.module_el8.10.0+3946+3de613d5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:redis-devel | 6.2.17-1.module_el8.10.0+3946+3de613d5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:redis-doc | 6.2.17-1.module_el8.10.0+3946+3de613d5 · AlmaLinux:8 | Package registry (OSV) |
| alpine:redis | 6.2.9-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:redis | 5:7.0.8-1 · Debian:12 | Package registry (OSV) |
| opensuse:redis | 6.2.6-150400.3.11.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:redis | 0:6.2.17-1.module+el8.10.0+22680+748527fd · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-debuginfo | 0:6.2.17-1.module+el8.10.0+22680+748527fd · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-debugsource | 0:6.2.17-1.module+el8.10.0+22680+748527fd · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-devel | 0:6.2.17-1.module+el8.10.0+22680+748527fd · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-doc | 0:6.2.17-1.module+el8.10.0+22680+748527fd · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:redis | 0:6.2.17-1.module+el8.10.0+1923+5b85c6a7 · Rocky Linux:8 | Package registry (OSV) |
| suse:redis | 6.2.6-150400.3.11.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.