Redislabs vulnerabilitiesNone on the known-exploited list.
Redislabs has 26 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Redis, with 22. If you run Redislabs software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Redislabs products have the most vulnerabilities?
Redis leads with 22 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Redislabs vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Redislabs's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Redislabs flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 59%CVE-2018-11218Critical
Memory 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 RC2 because of stack-based buffer overflows.
- 26%CVE-2019-10192High
A heap-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before 3.2.13, 4.x before 4.0.14 and 5.x before 5.0.4.
- 24%CVE-2018-12453High
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-service via an XGROUP command in which the key is not a stream.
- 24%CVE-2019-10193High
A stack-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before 3.2.13, 4.x before 4.0.14 and 5.x before 5.0.4.
- 15%CVE-2016-8339Critical
A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent.
- 9.5%CVE-2015-4335Critical
Redis before 2.8.21 and 3.x before 3.0.2 allows remote attackers to execute arbitrary Lua bytecode via the eval command.
- 7.0%CVE-2018-11219Critical
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 before 5.0 RC2, leading to a failure of bounds checking.
- 4.8%CVE-2021-21309High
Redis is an open-source, in-memory database that persists on disk.
- 4.6%CVE-2015-8080High
Integer overflow in the getnum function in lua_struct.c in Redis 2.8.x before 2.8.24 and 3.0.x before 3.0.6 allows context-dependent attackers with permission to run Lua code in a Redis session to cause a denial of...
All Redislabs products we track.
3 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Redislabs? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Memory 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 RC2 because of stack-based buffer overflows.
- Matched to
- Redis on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 26 published vulnerabilities across 3 products and 297 versions from Redislabs.
None of Redislabs's vulnerabilities is on the list of flaws known to be exploited today.
Redis, with 22 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Redislabs products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.