Buffer overflow in redis-cli of Redis before 4.0.10 and 5.x before 5.0 RC3 allows an attacker to achieve code execution and escalate to high
Noroxi assessment
Priority: Monitor (action score 34/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 85.5% of all records.
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: redis (Debian:12) 5:4.0.10-1; redis (Debian:8) 2:2.8.17-1+deb8u6; redis (Debian:9) 3:3.2.6-3+deb9u1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to redis (Debian:12) 5:4.0.10-1; redis (Debian:8) 2:2.8.17-1+deb8u6; redis (Debian:9) 3:3.2.6-3+deb9u1 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
Buffer overflow in redis-cli of Redis before 4.0.10 and 5.x before 5.0 RC3 allows an attacker to achieve code execution and escalate to higher privileges via a crafted command line. NOTE: It is unclear whether there are any common situations in which redis-cli is used with, for example, a -h (aka hostname) argument from an untrusted source.
- Published
- Jun 17, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-119
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redislabs redisbefore 4.0.10
- redislabs redis5.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | redis | before 5:4.0.10-1 | 5:4.0.10-1 |
| Debian:8 | redis | before 2:2.8.17-1+deb8u6 | 2:2.8.17-1+deb8u6 |
| Debian:9 | redis | before 3:3.2.6-3+deb9u1 | 3:3.2.6-3+deb9u1 |
| Red Hat:openstack:10::el7 | redis | before 0:3.0.6-4.el7ost | 0:3.0.6-4.el7ost |
| Red Hat:openstack:10::el7 | redis-debuginfo | before 0:3.0.6-4.el7ost | 0:3.0.6-4.el7ost |
| Red Hat:openstack:13::el7 | redis | before 0:3.2.8-3.el7ost | 0:3.2.8-3.el7ost |
| Red Hat:openstack:13::el7 | redis-debuginfo | before 0:3.2.8-3.el7ost | 0:3.2.8-3.el7ost |
| Red Hat:rhel_software_collections:3::el6 | rh-redis32-redis | before 0:3.2.13-1.el6 | 0:3.2.13-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-redis32-redis-debuginfo | before 0:3.2.13-1.el6 | 0:3.2.13-1.el6 |
| Red Hat:rhel_software_collections:3::el7 | rh-redis32-redis | before 0:3.2.13-1.el7 | 0:3.2.13-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-redis32-redis-debuginfo | before 0:3.2.13-1.el7 | 0:3.2.13-1.el7 |
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-2016-10517Oct 24, 2017 · networking.c in Redis before 3.2.7 allows "Cross Protocol Scripting" because it lacks a check for POST and Host: strings, which are not vali30Monitor
- ← EarlierCVE-2018-12453Jun 16, 2018 · Type confusion in the xgroupCommand function in t_stream.c in redis-server in Redis before 5.0 allows remote attackers to cause denial-of-se37Monitor
- Later →CVE-2018-11219Jun 17, 2018 · An Integer Overflow issue was discovered in the struct library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10, and 5.x befor41Plan
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 |
|---|---|---|
| debian:redis | 5:4.0.10-1 · Debian:12 | Package registry (OSV) |
| red hat:redis | 0:3.0.6-4.el7ost · Red Hat:openstack:10::el7 | Package registry (OSV) |
| red hat:redis-debuginfo | 0:3.0.6-4.el7ost · Red Hat:openstack:10::el7 | Package registry (OSV) |
| red hat:rh-redis32-redis | 0:3.2.13-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-redis32-redis-debuginfo | 0:3.2.13-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | local | 2018-06-18 |
| Proof-of-concept repository on GitHub | stars:0 | 2022-03-25 |
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.
- Published
- First PoC+1 d
- TodayOct 19, 2026+3046 d
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0555 · Jul 7, 2021(Philips Vue PAC Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- access.redhat.com/errata/RHSA-2019:0094
- access.redhat.com/errata/RHSA-2019:1860
- gist.github.com/fakhrizulkifli/f831f40ec6cde4f744c552503d8698f0
- github.com/antirez/redis/commit/9fdcc15962f9ff4baebe6fdd947816f43f730d50
- raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTES
- raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES
Vendor advisories and official records. Exploit/PoC links are deliberately left out.