redis - Debian Package Tracker

general

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

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

[pool directory]

o-o-stable: 3:3.2.6-3+deb9u3
o-o-sec: 3:3.2.6-3+deb9u9
o-o-bpo: 5:5.0.3-3~bpo9+2
oldstable: 5:5.0.3-4+deb10u3
old-sec: 5:5.0.14-1+deb10u2
old-bpo: 5:6.0.15-1~bpo10+1
stable: 5:6.0.16-1+deb11u2
stable-sec: 5:6.0.16-1+deb11u2
stable-bpo: 5:6.0.16-4~bpo11+1
testing: 5:6.0.16-4
unstable: 5:7.0.4-1

versioned links

3:3.2.6-3+deb9u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:3.2.6-3+deb9u9: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:4.0.11-2~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:5.0.3-3~bpo9+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:5.0.3-4+deb10u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:5.0.14-1+deb10u2: [.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:6.0.16-4~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:6.0.16-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.0.4-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

redis (1 bugs: 0, 0, 1, 0)
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: 2022-06-17 Last update: 2022-08-16 13:40

3 security issues in bookworm high

There are 3 open security issues in bookworm.

3 important 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-31144: Redis is an in-memory database that persists on disk. A specially crafted `XAUTOCLAIM` command on a stream key in a specific state may result with heap overflow, and potentially remote code execution. This problem affects versions on the 7.x branch prior to 7.0.4. The patch is released in version 7.0.4.

Created: 2022-07-04 Last update: 2022-08-01 13:40

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 2-day delay is over. Check why.

Created: 2022-07-21 Last update: 2022-08-16 15:06

Depends on packages which need a new maintainer normal

The packages that redis depends on which need a new maintainer are:

lua-bitop (#995502)
- Build-Depends: lua-bitop-dev

Created: 2021-10-02 Last update: 2022-08-16 14:02

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2022-06-11 Last update: 2022-08-16 12:59

2 low-priority security issues in bullseye low

There are 2 open security issues in bullseye.

2 issues left for the package maintainer to handle:

CVE-2022-24735: (needs triaging) 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: (needs triaging) 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.

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

Created: 2022-07-04 Last update: 2022-08-01 13:40

testing migrations

excuses:
- Migration status for redis (5:6.0.16-4 to 5:7.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ autopkgtest for python-fakeredis/1.6.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armel: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
- ∙ ∙ autopkgtest for python-redis/3.5.3-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armel: Regression ♻ (reference ♻), armhf: Not a regression, i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
- ∙ ∙ autopkgtest for redis/5:7.0.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redis.html
- ∙ ∙ 28 days old (needed 2 days)
- Not considered

news

[rss feed]

[2022-07-18] Accepted redis 5:7.0.4-1 (source) into unstable (Chris Lamb)
[2022-07-16] Accepted redis 5:7.0.3-1 (source) into unstable (Chris Lamb)
[2022-06-19] Accepted redis 5:7.0.2-2 (source) into unstable (Chris Lamb)
[2022-06-17] Accepted redis 5:7.0.2-1 (source) into unstable (Chris Lamb)
[2022-06-17] Accepted redis 5:7.0.1-4 (source) into unstable (Chris Lamb)
[2022-06-16] Accepted redis 5:7.0.1-3 (source) into experimental (Chris Lamb)
[2022-06-14] Accepted redis 5:7.0.1-2 (source) into experimental (Chris Lamb)
[2022-06-11] Accepted redis 5:7.0.1-1 (source) into experimental (Chris Lamb)
[2022-06-11] Accepted redis 5:6.0.16-4~bpo11+1 (source amd64 all) into bullseye-backports (Chris Lamb)
[2022-06-11] redis 5:6.0.16-4 MIGRATED to testing (Debian testing watch)
[2022-05-27] Accepted redis 5:6.0.16-4 (source) into unstable (Chris Lamb)
[2022-05-22] Accepted redis 5:6.0.16-3 (source) into unstable (Chris Lamb)
[2022-04-30] Accepted redis 5:7.0.0-1 (source) into experimental (Chris Lamb)
[2022-04-14] Accepted redis 5:7.0~rc3-1 (source) into experimental (Chris Lamb)
[2022-03-10] Accepted redis 5:6.0.16-2~bpo11+1 (source amd64 all) into bullseye-backports (Chris Lamb)
[2022-03-10] redis 5:6.0.16-2 MIGRATED to testing (Debian testing watch)
[2022-03-08] Accepted redis 5:7.0~rc2-2 (source) into experimental (Chris Lamb)
[2022-03-08] Accepted redis 5:6.0.16-2 (source) into unstable (Chris Lamb)
[2022-03-05] Accepted redis 5:7.0~rc2-1 (source) into experimental (Chris Lamb)
[2022-02-19] Accepted redis 5:5.0.14-1+deb10u2 (source amd64 all) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2022-02-19] Accepted redis 5:6.0.16-1+deb11u2 (source amd64 all) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2022-02-18] Accepted redis 5:5.0.14-1+deb10u2 (source amd64 all) into oldstable->embargoed, oldstable (Debian FTP Masters) (signed by: Chris Lamb)
[2022-02-18] Accepted redis 5:6.0.16-1+deb11u2 (source amd64 all) into stable-security->embargoed, stable-security (Debian FTP Masters) (signed by: Chris Lamb)
[2022-02-06] Accepted redis 5:7.0~rc1-1 (source) into experimental (Chris Lamb)
[2021-11-08] Accepted redis 3:3.2.6-3+deb9u9 (source amd64) into oldoldstable (Chris Lamb)
[2021-11-06] Accepted redis 5:5.0.14-1+deb10u1 (source amd64 all) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2021-11-06] Accepted redis 5:6.0.16-1+deb11u1 (source amd64 all) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2021-11-05] Accepted redis 5:5.0.14-1+deb10u1 (source amd64 all) into oldstable->embargoed, oldstable (Debian FTP Masters) (signed by: Chris Lamb)
[2021-11-05] Accepted redis 5:6.0.16-1+deb11u1 (source amd64 all) into stable-security->embargoed, stable-security (Debian FTP Masters) (signed by: Chris Lamb)
[2021-11-05] Accepted redis 3:3.2.6-3+deb9u8 (source amd64) into oldoldstable (Chris Lamb)

bugs [bug history graph]

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

links

homepage
lintian
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 5:6.0.16-1ubuntu1
23 bugs
patches for 5:6.0.16-1ubuntu1