Exposure of Resource to Wrong Sphere Affecting redis7 package, versions <7.0.8-150500.3.9.1


Severity

Recommended
medium

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

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-SLES155-REDIS7-6186428
  • published24 Jan 2024
  • disclosed23 Jan 2024

Introduced: 23 Jan 2024

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

How to fix?

Upgrade SLES:15.5 redis7 to version 7.0.8-150500.3.9.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream redis7 package and not the redis7 package as distributed by SLES. See How to fix? for SLES:15.5 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