CVE-2020-14147 json
An integer overflow in the getnum function in lua_struct.c in Redis before 6.0.3 allows context-dependent attackers with permission to run…
published 2020-06-15 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-6304
- cvss
- 7.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
An integer overflow in the getnum function in lua_struct.c in Redis before 6.0.3 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. NOTE: this issue exists because of a CVE-2015-8080 regression.
Patch / fix
- redislabs redis 5.0.9, 6.0.3
- redis Debian 14, Debian 13, Debian 12 5:6.0.0-1
debian advisories DEBIAN-CVE-2020-14147
- redis Package Hub 15 SP1, Package Hub 12, openSUSE Leap 15.1 4.0.14-bp151.3.6.1
opensuse advisories openSUSE-SU-2020:1035-1
- redis Alpine 3.24, Alpine 3.23, Alpine 3.22 +9 more 6.0.3-r0
alpine advisories ALPINE-CVE-2020-14147
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- github.com/antirez/redis@ef764dd commit
- github.com/antirez/redis#6875 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-14147 updated cvss 7.7
redis: integer overflow in the getnum function in lua_struct.c could lead to a DoS
-
Red Hat Enterprise Linux 8 redisaffected: workaround, no fix planned “There is no known mitigation for this issue, the flaw can only be resolved by applying updates.”
-
Red Hat OpenStack Platform 10 (Newton) redis Red Hat OpenStack Platform 13 (Queens) redisnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.08% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
Classification
- Weakness
- Technology feeds
References
-
github.com
/antirez/redis/pull/6875
patch, third-party-advisory
-
github.com
/antirez/redis/commit/ef764dde1cca2f25d00686673d1bc89448819571
patch, third-party-advisory
-
debian.org
/security/2020/dsa-4731
vendor-advisory, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-07/msg00058.html
vendor-advisory, mailing-list, third-party-advisory
-
security.gentoo.org
/glsa/202008-17
vendor-advisory, third-party-advisory
-
oracle.com
/security-alerts/cpujan2021.html
third-party-advisory
Sources
- CVE List CVE-2020-14147
- NVD CVE-2020-14147
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.