Exposure of Resource to Wrong Sphere Affecting redis-devel package, versions <0:6.2.17-1.module+el8.10.0+1923+5b85c6a7


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.05% (20th 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-ROCKY8-REDISDEVEL-8721626
  • published14 Feb 2025
  • disclosed18 Oct 2023

Introduced: 18 Oct 2023

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

How to fix?

Upgrade Rocky-Linux:8 redis-devel to version 0:6.2.17-1.module+el8.10.0+1923+5b85c6a7 or higher.
This issue was patched in RLSA-2025:0595.

NVD Description

Note: Versions mentioned in the description apply only to the upstream redis-devel package and not the redis-devel package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 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