Exposure of Resource to Wrong Sphere Affecting redis-doc package, versions <0:6.2.17-1.0.1.module+el8.10.0+90491+f9002f77


Severity

Recommended
high

Based on Oracle Linux 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-ORACLE8-REDISDOC-8661557
  • published25 Jan 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 Oracle:8 redis-doc to version 0:6.2.17-1.0.1.module+el8.10.0+90491+f9002f77 or higher.
This issue was patched in ELSA-2025-0595.

NVD Description

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