BIT-valkey-2023-45145

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/valkey/BIT-valkey-2023-45145.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-valkey-2023-45145
Aliases
Published
2024-08-22T19:40:22.448Z
Modified
2024-08-23T07:12:28.072526Z
Summary
[none]
Details

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.

Database specific
{
    "cpes": [
        "cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*",
        "cpe:2.3:a:redis:redis:2.6.0:rc1:*:*:*:*:*:*"
    ],
    "severity": "Low"
}
References

Affected packages

Bitnami / valkey

Package

Name
valkey
Purl
pkg:bitnami/valkey

Severity

  • 3.6 (Low) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
2.6.0
Fixed
6.2.14
Introduced
7.0.0
Fixed
7.0.14
Introduced
7.2.0
Fixed
7.2.2
Type
SEMVER
Events
Introduced
2.6.0-rc1
Last affected
2.6.0-rc1