An update for redis is now available for openEuler-20.03-LTS and openEuler-20.03-LTS-SP1 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2021-1093 Final 1.0 1.0 2021-03-26 Initial 2021-03-26 2021-03-26 openEuler SA Tool V1.0 2021-03-26 redis security update An update for redis is now available for openEuler-20.03-LTS and openEuler-20.03-LTS-SP1. Redis is an advanced key-value store. It is often referred to as a dattructure server since keys can contain strings, hashes ,lists, sets anorted sets. Security Fix(es): Redis is an open-source, in-memory database that persists on disk. In affected versions of Redis an integer overflow bug in 32-bit Redis version 4.0 or newer could be exploited to corrupt the heap and potentially result with remote code execution. Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. We believe this could in certain conditions be exploited for remote code execution. By default, authenticated Redis users have access to all configuration parameters and can therefore use the “CONFIG SET proto-max-bulk-len” to change the safe default, making the system vulnerable. **This problem only affects 32-bit Redis (on a 32-bit system, or as a 32-bit executable running on a 64-bit system).** The problem is fixed in version 6.2, and the fix is back ported to 6.0.11 and 5.0.11. Make sure you use one of these versions if you are running 32-bit Redis. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent clients from directly executing `CONFIG SET`: Using Redis 6.0 or newer, ACL configuration can be used to block the command. Using older versions, the `rename-command` configuration directive can be used to rename the command to a random string unknown to users, rendering it inaccessible. Please note that this workaround may have an additional impact on users or operational systems that expect `CONFIG SET` to behave in certain ways.(CVE-2021-21309) An update for redis is now available for openEuler-20.03-LTS and openEuler-20.03-LTS-SP1. openEuler Security has rated this update as having a security impact of critical. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Critical redis https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1093 https://openeuler.org/en/security/cve/detail.html?id=CVE-2021-21309 https://nvd.nist.gov/vuln/detail/CVE-2021-21309 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 redis-debuginfo-4.0.11-13.oe1.aarch64.rpm redis-4.0.11-13.oe1.aarch64.rpm redis-debugsource-4.0.11-13.oe1.aarch64.rpm redis-debugsource-4.0.11-13.oe1.aarch64.rpm redis-debuginfo-4.0.11-13.oe1.aarch64.rpm redis-4.0.11-13.oe1.aarch64.rpm redis-4.0.11-13.oe1.src.rpm redis-4.0.11-13.oe1.src.rpm redis-debugsource-4.0.11-13.oe1.x86_64.rpm redis-4.0.11-13.oe1.x86_64.rpm redis-debuginfo-4.0.11-13.oe1.x86_64.rpm redis-4.0.11-13.oe1.x86_64.rpm redis-debuginfo-4.0.11-13.oe1.x86_64.rpm redis-debugsource-4.0.11-13.oe1.x86_64.rpm Redis is an open-source, in-memory database that persists on disk. In affected versions of Redis an integer overflow bug in 32-bit Redis version 4.0 or newer could be exploited to corrupt the heap and potentially result with remote code execution. Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. We believe this could in certain conditions be exploited for remote code execution. By default, authenticated Redis users have access to all configuration parameters and can therefore use the “CONFIG SET proto-max-bulk-len” to change the safe default, making the system vulnerable. **This problem only affects 32-bit Redis (on a 32-bit system, or as a 32-bit executable running on a 64-bit system).** The problem is fixed in version 6.2, and the fix is back ported to 6.0.11 and 5.0.11. Make sure you use one of these versions if you are running 32-bit Redis. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent clients from directly executing `CONFIG SET`: Using Redis 6.0 or newer, ACL configuration can be used to block the command. Using older versions, the `rename-command` configuration directive can be used to rename the command to a random string unknown to users, rendering it inaccessible. Please note that this workaround may have an additional impact on users or operational systems that expect `CONFIG SET` to behave in certain ways. 2021-03-26 CVE-2021-21309 openEuler-20.03-LTS openEuler-20.03-LTS-SP1 Critical 9.8 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H redis security update 2021-03-26 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1093