# CVE-2015-8080: Integer overflow in n/a

> An integer overflow in Redis allows attackers with Lua execution permissions to cause denial of service or potentially execute code via stack-based buffer overflow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2016
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2015-8080, CLEANSTART-2026-KD93990, DEBIAN-CVE-2015-8080, DSA-3412-1, GHSA-4r9x-2fwv-q8g6, MGASA-2015-0472, RHSA-2016:0095, RHSA-2016:0096, RHSA-2016:0097, UBUNTU-CVE-2015-8080

## What is CVE-2015-8080?

CVE-2015-8080 is a high-severity vulnerability in Debian Debian Linux, published on 13 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2015-8080?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | Red Hat:openstack-optools:7::el7 | All versions | 0:2.8.24-1.el7ost |
| `redis-debuginfo` | Red Hat:openstack-optools:7::el7 | All versions | 0:2.8.24-1.el7ost |
| `redis` | Red Hat:openstack:6::el7 | All versions | 0:2.8.24-1.el7ost |
| `redis-debuginfo` | Red Hat:openstack:6::el7 | All versions | 0:2.8.24-1.el7ost |
| `redis` | Red Hat:openstack:7::el7 | All versions | 0:2.8.24-1.el7ost |
| `redis-debuginfo` | Red Hat:openstack:7::el7 | All versions | 0:2.8.24-1.el7ost |

Products: Debian Debian Linux, Opensuse Leap, Opensuse Opensuse, Redhat Openstack, Redislabs Redis.

## How do I fix CVE-2015-8080?

Upgrade to a fixed version.

## Is CVE-2015-8080 being exploited?

There is no known exploitation of CVE-2015-8080 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8080 and fix it if it is affected.

What it is: CVE-2015-8080 is a high-severity vulnerability in Debian Debian Linux, published on 13 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8080 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-8080/ (Markdown: https://insights.sbomify.com/CVE-2015-8080/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-8080
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-8080
- OSV: https://osv.dev/vulnerability/CVE-2015-8080

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-8080/
Summaries are generated and may contain mistakes; the official description above is the record.