Bug 816282 (CVE-2021-32626, CVE-2021-32627, CVE-2021-32628, CVE-2021-32672, CVE-2021-32675, CVE-2021-32687, CVE-2021-32762, CVE-2021-41099) – <dev-db/redis-{5.0.14, 6.0.16, 6.2.6}: multiple vulnerabilities (CVE-2021-{32626,32627,32628,32672,32675,32687,32762,41099})

• Product: Gentoo Security
• Status: IN_PROGRESS ---

[Description Sam James 2021-10-04 20:09:19 UTC]

CVE-2021-32626 (https://github.com/redis/redis/commit/666ed7facf4524bf6d19b11b20faa2cf93fdf591):

Redis is an open source, in-memory database that persists on disk. In affected versions specially crafted Lua scripts executing in Redis can cause the heap-based Lua stack to be overflowed, due to incomplete checks for this condition. This can result with heap corruption and potentially remote code execution. This problem exists in all versions of Redis with Lua scripting support, starting from 2.6. The problem is fixed in versions 6.2.6, 6.0.16 and 5.0.14. For users unable to update an additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.

CVE-2021-32627 (https://github.com/redis/redis/commit/f6a40570fa63d5afdd596c78083d754081d80ae3):

Redis is an open source, in-memory database that persists on disk. In affected versions an integer overflow bug in Redis can be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves changing the default proto-max-bulk-len and client-query-buffer-limit configuration parameters to very large values and constructing specially crafted very large stream elements. The problem is fixed in Redis 6.2.6, 6.0.16 and 5.0.14. For users unable to upgrade an additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the proto-max-bulk-len configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.

CVE-2021-32628 (https://github.com/redis/redis/commit/f6a40570fa63d5afdd596c78083d754081d80ae3):

Redis is an open source, in-memory database that persists on disk. An integer overflow bug in the ziplist data structure used by all versions of Redis can be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves modifying the default ziplist configuration parameters (hash-max-ziplist-entries, hash-max-ziplist-value, zset-max-ziplist-entries or zset-max-ziplist-value) to a very large value, and then constructing specially crafted commands to create very large ziplists. The problem is fixed in Redis versions 6.2.6, 6.0.16, 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the above configuration parameters. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.

CVE-2021-32672 (https://github.com/redis/redis/security/advisories/GHSA-9mj9-xx53-qmxm):

Redis is an open source, in-memory database that persists on disk. When using the Redis Lua Debugger, users can send malformed requests that cause the debugger’s protocol parser to read data beyond the actual buffer. This issue affects all versions of Redis with Lua debugging support (3.2 or newer). The problem is fixed in versions 6.2.6, 6.0.16 and 5.0.14.

CVE-2021-32675 (https://github.com/redis/redis/commit/5674b0057ff2903d43eaff802017eddf37c360f8):

Redis is an open source, in-memory database that persists on disk. When parsing an incoming Redis Standard Protocol (RESP) request, Redis allocates memory according to user-specified values which determine the number of elements (in the multi-bulk header) and size of each element (in the bulk header). An attacker delivering specially crafted requests over multiple connections can cause the server to allocate significant amount of memory. Because the same parsing mechanism is used to handle authentication requests, this vulnerability can also be exploited by unauthenticated users. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate this problem without patching the redis-server executable is to block access to prevent unauthenticated users from connecting to Redis. This can be done in different ways: Using network access control tools like firewalls, iptables, security groups, etc. or Enabling TLS and requiring users to authenticate using client side certificates.

CVE-2021-32687 (https://github.com/redis/redis/security/advisories/GHSA-m3mf-8x9w-r27q):

Redis is an open source, in-memory database that persists on disk. An integer overflow bug affecting all versions of Redis can be exploited to corrupt the heap and potentially be used to leak arbitrary contents of the heap or trigger remote code execution. The vulnerability involves changing the default set-max-intset-entries configuration parameter to a very large value and constructing specially crafted commands to manipulate sets. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the set-max-intset-entries configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.

CVE-2021-32762 (https://github.com/redis/redis/security/advisories/GHSA-833w-8v3m-8wwr):

Redis is an open source, in-memory database that persists on disk. The redis-cli command line tool and redis-sentinel service may be vulnerable to integer overflow when parsing specially crafted large multi-bulk network replies. This is a result of a vulnerability in the underlying hiredis library which does not perform an overflow check before calling the calloc() heap allocation function. This issue only impacts systems with heap allocators that do not perform their own overflow checks. Most modern systems do and are therefore not likely to be affected. Furthermore, by default redis-sentinel uses the jemalloc allocator which is also not vulnerable. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14.

[Comment 1 Larry the Git Cow 2021-10-04 21:53:40 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc34d8257d01cf57f9b1f41201a124eab61fefdf

commit cc34d8257d01cf57f9b1f41201a124eab61fefdf
Author:     Sam James <[e-mail]>
AuthorDate: 2021-10-04 21:53:25 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2021-10-04 21:53:25 +0000

    dev-db/redis: add 6.2.6
    
    Bug: https://bugs.gentoo.org/816282
    Signed-off-by: Sam James <[e-mail]>

 dev-db/redis/Manifest           |   1 +
 dev-db/redis/redis-6.2.6.ebuild | 189 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 190 insertions(+)

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2d75e6d77c83f356a052d82a2581aeda748fa9c

commit c2d75e6d77c83f356a052d82a2581aeda748fa9c
Author:     Sam James <[e-mail]>
AuthorDate: 2021-10-04 21:53:22 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2021-10-04 21:53:22 +0000

    dev-db/redis: add 6.0.16
    
    Bug: https://bugs.gentoo.org/816282
    Signed-off-by: Sam James <[e-mail]>

 dev-db/redis/Manifest            |   1 +
 dev-db/redis/redis-6.0.16.ebuild | 189 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 190 insertions(+)

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d9573dfe0717cec68a1e3f6454e8b9aa72ec9655

commit d9573dfe0717cec68a1e3f6454e8b9aa72ec9655
Author:     Sam James <[e-mail]>
AuthorDate: 2021-10-04 21:53:18 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2021-10-04 21:53:18 +0000

    dev-db/redis: add 5.0.14
    
    Bug: https://bugs.gentoo.org/816282
    Signed-off-by: Sam James <[e-mail]>

 dev-db/redis/Manifest            |   1 +
 dev-db/redis/redis-5.0.14.ebuild | 164 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 165 insertions(+)

[Comment 2 Sam James 2021-10-05 03:57:55 UTC]

CVE-2021-41099 (https://github.com/redis/redis/security/advisories/GHSA-j3cr-9h5g-6cph):

Redis is an open source, in-memory database that persists on disk. An integer overflow bug in the underlying string library can be used to corrupt the heap and potentially result with denial of service or remote code execution. The vulnerability involves changing the default proto-max-bulk-len configuration parameter to a very large value and constructing specially crafted network payloads or commands. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the proto-max-bulk-len configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.

[Comment 3 John Helmert III 2021-11-20 17:19:44 UTC]

Please cleanup

[Comment 4 Larry the Git Cow 2022-01-01 09:38:53 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ead0cbbf6bca2037bdd280f55ce9a0a93f933220

commit ead0cbbf6bca2037bdd280f55ce9a0a93f933220
Author:     Sam James <[e-mail]>
AuthorDate: 2022-01-01 09:36:47 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2022-01-01 09:38:34 +0000

    dev-db/redis: drop 5.0.13, 6.0.15, 6.2.5
    
    Bug: https://bugs.gentoo.org/816282
    Signed-off-by: Sam James <[e-mail]>

 dev-db/redis/Manifest            |   3 -
 dev-db/redis/redis-5.0.13.ebuild | 164 ---------------------------------
 dev-db/redis/redis-6.0.15.ebuild | 189 ---------------------------------------
 dev-db/redis/redis-6.2.5.ebuild  | 189 ---------------------------------------
 4 files changed, 545 deletions(-)