CVE-2021-21309: Integer overflow on 32-bit systems
Noroxi assessment
Priority: Monitor (action score 36/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: 4.7% (FIRST EPSS); higher than 92% of all records.
- Anyone who can reach it over the internet 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 redis 6.2.
- Severity is disputed: the assigning authority (CNA) scores it 5.4, NVD 8.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to redis redis 6.2 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 open-source, in-memory database that persists on disk. In affected versions of Redis an integer overflow bug in 32-bit Redis version 4.0 or newer could be exploited to corrupt the heap and potentially result with remote code execution. Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. We believe this could in certain conditions be exploited for remote code execution. By default, authenticated Redis users have access to all configuration parameters and can therefore use the “CONFIG SET proto-max-bulk-len” to change the safe default, making the system vulnerable. **This problem only affects 32-bit Redis (on a 32-bit system, or as a 32-bit executable running on a 64-bit system).** The problem is fixed in version 6.2, and the fix is back ported to 6.0.11 and 5.0.11. Make sure you use one of these versions if you are running 32-bit Redis. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent clients from directly executing `CONFIG SET`: Using Redis 6.0 or newer, ACL configuration can be used to block the command. Using older versions, the `rename-command` configuration directive can be used to rename the command to a random string unknown to users, rendering it inaccessible. Please note that this workaround may have an additional impact on users or operational systems that expect `CONFIG SET` to behave in certain ways.
- Published
- Feb 26, 2021
- Updated
- Jun 16, 2026
- EPSS
- 4.7% · 92th percentile
- CWE
- CWE-190
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.7%
CNA vs NVD score
- NVD
- 8.8
- CNA · GitHub_M
- 5.4
- 3.4 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
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 |
|---|---|---|
| redislabs | redis | cpe:2.3:a:redislabs: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
- < 5.0.11, >= 6.0.0, < 6.0.11affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redislabs redis4.0 and later · before 5.0.11
- redislabs redis6.0.0 and later · before 6.0.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | redis | from 4.0 · before 5.0.11-r0 | 5.0.11-r0 |
| Alpine:v3.13 | redis | from 4.0 · before 6.0.11-r0 | 6.0.11-r0 |
| Alpine:v3.14 | redis | from 4.0 · before 6.2.0-r0 | 6.2.0-r0 |
| Debian:12 | redis | before 5:6.0.11-1 | 5:6.0.11-1 |
| Debian:9 | redis | before 3:3.2.6-3+deb9u4 | 3:3.2.6-3+deb9u4 |
| openSUSE:Leap 15.2 | redis | before 6.0.13-lp152.2.3.1 | 6.0.13-lp152.2.3.1 |
| openSUSE:Tumbleweed | redis | before 6.2.5-1.2 | 6.2.5-1.2 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP2 | redis | before 6.0.13-1.10.1 | 6.0.13-1.10.1 |
Same product
redislabs: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-11218Memory Corruption was discovered in the cmsgpack library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10, and 5.x before 5.0…60This week
- CVE-2016-8339A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent.43Plan
- CVE-2015-4335Redis before 2.8.21 and 3.x before 3.0.2 allows remote attackers to execute arbitrary Lua bytecode via the eval command.43Plan
Published before and after this one in the same product
- ← EarlierCVE-2013-0180Nov 1, 2019 · Insecure temporary file vulnerability in Redis 2.6 related to /tmp/redis.ds.22Monitor
- ← EarlierCVE-2020-14147Jun 15, 2020 · An integer overflow in the getnum function in lua_struct.c in Redis before 6.0.3 allows context-dependent attackers with permission to run…31Monitor
- Later →CVE-2021-3470Mar 31, 2021 · A heap overflow issue was found in Redis in versions before 5.0.10, before 6.0.9 and before 6.2.0 when using a heap allocator other than…21Monitor
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 |
|---|---|---|
| redis redis | 6.2 · description | Vendor (CNA) |
| alpine:redis | 5.0.11-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:redis | 5:6.0.11-1 · Debian:12 | Package registry (OSV) |
| opensuse:redis | 6.0.13-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:redis | 6.0.13-1.10.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP2 | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0165 · Feb 23, 2021(Redis Labs Güvenlik Güncellemesi Yayınladı)
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.