CVE-2016-8339: A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent.
Critical CVSS 9.8
- CVE id
- CVE-2016-8339
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Redis Runtimes and servers |
3.2.0 3.2.1 3.2.2 3.2.3 |
not fixed yet |
How to fix it
No fix yet. No fixed Redis release is listed yet.
redis-server --version
- Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
- Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
- Install the patched Redis release of your series (the redis image tag or your packages) and restart it; on a managed service, apply the provider's maintenance update.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent. An out of bounds write vulnerability exists in the handling of the client-output-buffer-limit option during the CONFIG SET command for the Redis data structure store. A crafted CONFIG SET command can lead to an out of bounds write potentially resulting in code execution.
References
- CVE-2016-8339 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2016-8339
- Web: https://github.com/antirez/redis/commit/6d9f8e2462fc2c426d48c941edeb78e5df7d2977
- Web: https://security.gentoo.org/glsa/201702-16
- Web: https://github.com/antirez/redis/commit/6d9f8e2462fc2c426d48c941edeb78e5df7d2977
- Web: https://security.gentoo.org/glsa/201702-16
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.