CVE-2023-45145

Redis is an in-memory database that persists on disk. On startup, Redis begins listening on a Unix socket before adjusting its permissions to the user-provided configuration. If a permissive umask(2) is used, this creates a race condition that enables, during a short period of time, another process to establish an otherwise unauthorized connection. This problem has existed since Redis 2.6.0-RC1. This issue has been addressed in Redis versions 7.2.2, 7.0.14 and 6.2.14. Users are advised to upgrade. For users unable to upgrade, it is possible to work around the problem by disabling Unix sockets, starting Redis with a restrictive umask, or storing the Unix socket file in a protected directory.

References

Affected packages

Git / github.com/redis/redis

Affected ranges

Type: GIT
Repo: https://github.com/redis/redis
Events: Introduced

7c5d96d98e6cc2a0e7ea5ea30e3ca4772a84b3cb

Fixed

91863dd854feba7f75ae58976a920acb192a5b67

Type: GIT
Repo: https://github.com/redis/redis
Events: Introduced

d375595d5e3ae2e5c29e6c00a2dc3d60578fd9fc

Fixed

c1d92a69c62c6577dc118da0833b01a793322542

Affected versions

7.*

7.0.0

7.0.1

7.0.10

7.0.11

7.0.12

7.0.13

7.0.2

7.0.3

7.0.4

7.0.5

7.0.6

7.0.7

7.0.8

7.0.9

Database specific

{
    "unresolved_versions": [
        {
            "type": "",
            "events": [
                {
                    "introduced": "7.1.0"
                },
                {
                    "fixed": "7.2.2"
                }
            ]
        }
    ]
}