redis - Debian Package Tracker

general

source: redis (main)
version: 5:7.0.13-1
maintainer: Chris Lamb (DMD)
arch: all any
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 5:5.0.14-1+deb10u2
o-o-sec: 5:5.0.14-1+deb10u4
o-o-bpo: 5:6.0.15-1~bpo10+1
oldstable: 5:6.0.16-1+deb11u2
old-sec: 5:6.0.16-1+deb11u2
old-bpo: 5:7.0.10-1~bpo11+1
stable: 5:7.0.11-1
testing: 5:7.0.13-1
unstable: 5:7.0.13-1
exp: 5:7.2.1-1

versioned links

5:5.0.14-1+deb10u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:5.0.14-1+deb10u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:6.0.15-1~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:6.0.16-1+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.0.10-1~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.0.11-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.0.13-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.2.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

redis
redis-sentinel
redis-server (5 bugs: 0, 5, 0, 0)
redis-tools

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2023-09-09 Last update: 2023-10-01 06:30

lintian reports 1 error high

Lintian reports 1 error about this package. You should make the package lintian clean getting rid of them.

Created: 2023-09-09 Last update: 2023-09-09 11:05

8 low-priority security issues in bullseye low

There are 8 open security issues in bullseye.

5 issues left for the package maintainer to handle:

CVE-2021-31294: (needs triaging) Redis before 6cbea7d allows a replica to cause an assertion failure in a primary server by sending a non-administrative command (specifically, a SET command). NOTE: this was fixed for Redis 6.2.x and 7.x in 2021. Versions before 6.2 were not intended to have safety guarantees related to this.
CVE-2022-24834: (needs triaging) Redis is an in-memory database that persists on disk. A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson library, and result with heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. The problem is fixed in versions 7.0.12, 6.2.13, and 6.0.20.
CVE-2022-36021: (needs triaging) Redis is an in-memory database that persists on disk. Authenticated users can use string matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. The problem is fixed in Redis versions 6.0.18, 6.2.11, 7.0.9.
CVE-2023-25155: (needs triaging) Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. This problem affects all Redis versions. Patches were released in Redis version(s) 6.0.18, 6.2.11 and 7.0.9.
CVE-2023-28856: (needs triaging) Redis is an open source, in-memory database that persists on disk. Authenticated users can use the `HINCRBYFLOAT` command to create an invalid hash field that will crash Redis on access in affected versions. This issue has been addressed in in versions 7.0.11, 6.2.12, and 6.0.19. Users are advised to upgrade. There are no known workarounds for this issue.

You can find information about how to handle these issues in the security team's documentation.

3 ignored issues:

CVE-2022-24735: Redis is an in-memory database that persists on disk. By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis prior to version 7.0.0 or 6.2.7 can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. The Lua script execution environment in Redis provides some measures that prevent a script from creating side effects that persist and can affect the execution of the same, or different script, at a later time. Several weaknesses of these measures have been publicly known for a long time, but they had no security impact as the Redis security model did not endorse the concept of users or privileges. With the introduction of ACLs in Redis 6.0, these weaknesses can be exploited by a less privileged users to inject Lua code that will execute at a later time, when a privileged user executes a Lua script. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.
CVE-2022-24736: Redis is an in-memory database that persists on disk. Prior to versions 6.2.7 and 7.0.0, an attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result with a crash of the redis-server process. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.
CVE-2022-35977: Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted `SETRANGE` and `SORT(_RO)` commands can trigger an integer overflow, resulting with Redis attempting to allocate impossible amounts of memory and abort with an out-of-memory (OOM) panic. The problem is fixed in Redis versions 7.0.8, 6.2.9 and 6.0.17. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Created: 2022-07-04 Last update: 2023-09-12 12:00

3 low-priority security issues in bookworm low

There are 3 open security issues in bookworm.

3 issues left for the package maintainer to handle:

CVE-2022-24834: (needs triaging) Redis is an in-memory database that persists on disk. A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson library, and result with heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. The problem is fixed in versions 7.0.12, 6.2.13, and 6.0.20.
CVE-2023-36824: (needs triaging) Redis is an in-memory database that persists on disk. In Redit 7.0 prior to 7.0.12, extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption and potentially remote code execution. Several scenarios that may lead to authenticated users executing a specially crafted `COMMAND GETKEYS` or `COMMAND GETKEYSANDFLAGS`and authenticated users who were set with ACL rules that match key names, executing a specially crafted command that refers to a variadic list of key names. The vulnerability is patched in Redis 7.0.12.
CVE-2023-41053: (needs triaging) Redis is an in-memory database that persists on disk. Redis does not correctly identify keys accessed by `SORT_RO` and as a result may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. The problem exists in Redis 7.0 or newer and has been fixed in Redis 7.0.13 and 7.2.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

You can find information about how to handle these issues in the security team's documentation.

Created: 2023-07-11 Last update: 2023-09-12 12:00

debian/patches: 3 patches to forward upstream low

Among the 5 debian patches available in version 5:7.0.13-1 of the package, we noticed the following issues:

3 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2023-09-09 09:42

news

[rss feed]

[2023-09-11] redis 5:7.0.13-1 MIGRATED to testing (Debian testing watch)
[2023-09-08] Accepted redis 5:7.2.1-1 (source) into experimental (Chris Lamb)
[2023-09-08] Accepted redis 5:7.0.13-1 (source) into unstable (Chris Lamb)
[2023-08-27] redis 5:7.0.12-2 MIGRATED to testing (Debian testing watch)
[2023-08-24] Accepted redis 5:7.2.0-2 (source) into experimental (Chris Lamb)
[2023-08-24] Accepted redis 5:7.0.12-2 (source) into unstable (Chris Lamb)
[2023-08-18] Accepted redis 5:7.2.0-1 (source) into experimental (Chris Lamb)
[2023-07-19] redis 5:7.0.12-1 MIGRATED to testing (Debian testing watch)
[2023-07-12] Accepted redis 5:7.2-rc3-1 (source) into experimental (Chris Lamb)
[2023-07-12] Accepted redis 5:7.0.12-1 (source) into unstable (Chris Lamb)
[2023-05-29] Accepted redis 5:7.2-rc2-1 (source) into experimental (Chris Lamb)
[2023-05-02] redis 5:7.0.11-1 MIGRATED to testing (Debian testing watch)
[2023-04-21] Accepted redis 5:5.0.14-1+deb10u4 (source amd64 all) into oldstable (Chris Lamb)
[2023-04-20] Accepted redis 5:7.0.11-1 (source) into unstable (Chris Lamb)
[2023-04-01] Accepted redis 5:7.0.10-1~bpo11+1 (source amd64 all) into bullseye-backports (Chris Lamb)
[2023-04-01] redis 5:7.0.10-1 MIGRATED to testing (Debian testing watch)
[2023-03-25] Accepted redis 5:7.0.10-1 (source) into unstable (Chris Lamb)
[2023-03-25] Accepted redis 5:7.2~rc1-1 (source) into experimental (Chris Lamb)
[2023-03-13] Accepted redis 5:5.0.14-1+deb10u3 (source amd64 all) into oldstable (Chris Lamb)
[2023-03-04] Accepted redis 5:7.0.9-1 (source) into unstable (Chris Lamb)
[2023-02-22] Accepted redis 5:7.0.8-4 (source) into unstable (Chris Lamb)
[2023-02-13] Accepted redis 5:7.0.8-3 (source) into unstable (Chris Lamb)
[2023-01-30] Accepted redis 5:7.0.8-2 (source amd64 all) into unstable (Chris Lamb)
[2023-01-22] Accepted redis 5:7.0.8-1 (source) into unstable (Chris Lamb)
[2022-12-26] Accepted redis 5:7.0.7-1~bpo11+1 (source amd64 all) into bullseye-backports (Chris Lamb)
[2022-12-26] redis 5:7.0.7-1 MIGRATED to testing (Debian testing watch)
[2022-12-17] Accepted redis 5:7.0.7-1 (source) into unstable (Chris Lamb)
[2022-09-27] Accepted redis 5:7.0.5-1~bpo11+1 (source amd64 all) into bullseye-backports (Chris Lamb)
[2022-09-27] redis 5:7.0.5-1 MIGRATED to testing (Debian testing watch)
[2022-09-23] Accepted redis 5:7.0.5-1 (source) into unstable (Chris Lamb)

bugs [bug history graph]

all: 6
RC: 1
I&N: 5
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (1, 0)
buildd: logs, exp, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 5:7.0.12-1
23 bugs