Skip to content
Noroxi
CVE-2015-8080· NVD / CVE Program· CNA mitre

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 attacke

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 service (memory corruption and application crash) or possibly bypass intended sandbox restrictions via a large number, which triggers a stack-based buffer overflow.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Apr 13, 2016
Updated
Jun 16, 2026
EPSS
4.6% · 91th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.6%

Affected systems

VendorProduct
redislabsredis
debiandebian linux
opensuseleap
opensuseopensuse
redhatopenstack

Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redislabs redis2.8.0 and later · before 2.8.24
  • redislabs redis3.0.0 and later · before 3.0.6
  • redislabs redis5.0.0 and later · before 5.0.8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10redisfrom 2.8.0 · before 5.0.5-r15.0.5-r1
Alpine:v3.11redisfrom 2.8.0 · before 5.0.7-r15.0.7-r1
Alpine:v3.12redisfrom 2.8.0 · before 5.0.8-r05.0.8-r0
Debian:12redisbefore 2:3.0.5-42:3.0.5-4
Debian:8redisbefore 2:2.8.17-1+deb8u32:2.8.17-1+deb8u3
openSUSE:Tumbleweedredisbefore 6.2.5-1.26.2.5-1.2
Red Hat:openstack:6::el7redisbefore 0:2.8.24-1.el7ost0:2.8.24-1.el7ost
Red Hat:openstack:6::el7redis-debuginfobefore 0:2.8.24-1.el7ost0:2.8.24-1.el7ost
SUSE:Linux Enterprise Module for Server Applications 15 SP2redisbefore 6.0.8-1.3.16.0.8-1.3.1

Other 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
    57Plan
  • 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
  • CVE-2018-11219An 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 befor
    41Plan
  • CVE-2017-15047The clusterLoadConfig function in cluster.c in Redis 4.0.2 allows attackers to cause a denial of service (out-of-bounds array index and appl
    40Plan
  • CVE-2021-32761Integer overflow issues with *BIT commands on 32-bit systems
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:redis5.0.5-r1 · Alpine:v3.10Package registry (OSV)
debian:redis2:3.0.5-4 · Debian:12Package registry (OSV)
opensuse:redis6.2.5-1.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:redis0:2.8.24-1.el7ost · Red Hat:openstack:6::el7Package registry (OSV)
red hat:redis-debuginfo0:2.8.24-1.el7ost · Red Hat:openstack:6::el7Package registry (OSV)
suse:redis6.0.8-1.3.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP2Package 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.

EPSS, last 120 days-1% in 7 days

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.

No commit or PR link among the references.

Finders, 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).

Technical details

Attack conditions

  • Anyone who can reach it over the internet 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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/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.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records