CVE-2015-8080: Buffer Overflow

Published Apr 13, 2016
·
Updated

Integer overflow in the getnum function in luastruct.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.

Affected Software

9 affected components
Redislabs Redis>=2.8.0<2.8.24
Redislabs Redis>=3.0.0<3.0.6
Redislabs Redis>=5.0.0<5.0.8
Debian Debian Linux=8.0
Debian Debian Linux=9.0
openSUSE Leap=42.1
openSUSE openSUSE=13.2
redhat Openstack=6.0
redhat Openstack=7.0

Event History

Apr 13, 2016
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2015-8080?

CVE-2015-8080 has a high severity due to its potential for denial of service and memory corruption.

2

How do I fix CVE-2015-8080?

To fix CVE-2015-8080, upgrade Redis to version 2.8.24 or 3.0.6 or later.

3

What versions of Redis are affected by CVE-2015-8080?

CVE-2015-8080 affects Redis versions before 2.8.24 and 3.0.6.

4

Can CVE-2015-8080 allow bypassing the Redis sandbox?

Yes, CVE-2015-8080 may potentially allow attackers to bypass the intended Redis sandbox.

5

What impact does CVE-2015-8080 have on systems running Redis?

CVE-2015-8080 can lead to application crashes and possible exploitation of systems running vulnerable Redis versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203