Improper Privilege Management Affecting redis-devel package, versions *


Severity

Recommended
0.0
low
0
10

Based on CentOS security rating

    Threat Intelligence

    EPSS
    0.04% (11th 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 ID SNYK-CENTOS8-REDISDEVEL-6012337
  • published 19 Oct 2023
  • disclosed 18 Oct 2023

How to fix?

There is no fixed version for Centos:8 redis-devel.

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 Centos. See How to fix? for Centos: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
Expand this section

NVD

3.6 low
  • Attack Vector (AV)
    Local
  • Attack Complexity (AC)
    High
  • Privileges Required (PR)
    Low
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    Low
  • Integrity (I)
    Low
  • Availability (A)
    None
Expand this section

Red Hat

3.6 low
Expand this section

SUSE

7 high