Exposure of Resource to Wrong Sphere Affecting redis:7/redis-doc package, versions <0:7.2.6-1.module_el9.5.0+130+36ae7635


Severity

Recommended
medium

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.04% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX9-REDIS-8492571
  • published10 Dec 2024
  • disclosed5 Dec 2024

Introduced: 5 Dec 2024

NewCVE-2023-45145  (opens in a new tab)
CWE-668  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:9 redis:7/redis-doc to version 0:7.2.6-1.module_el9.5.0+130+36ae7635 or higher.
This issue was patched in ALSA-2024:10869.

NVD Description

Note: Versions mentioned in the description apply only to the upstream redis:7/redis-doc package and not the redis:7/redis-doc package as distributed by AlmaLinux. See How to fix? for AlmaLinux:9 relevant fixed versions and status.

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.

CVSS Scores

version 3.1