Summaryinfo

A vulnerability has been found in Redis up to 6.2.13/7.0.13/7.2.1 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to exposure of resource. This vulnerability is listed as CVE-2023-45145. The attack must be carried out locally. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Redis up to 6.2.13/7.0.13/7.2.1. This issue affects an unknown part. The manipulation with an unknown input leads to a exposure of resource vulnerability. Using CWE to declare the problem leads to CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was presented 10/19/2023 as GHSA-ghmp-889m-7cvx. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-45145 since 10/04/2023. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 212120 (RHEL 9 : redis:7 (RHSA-2024:10869)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.2.14, 7.0.14 or 7.2.2 eliminates this vulnerability. Applying the patch 03345ddc7faf7af079485f2cbe5d17a1611cbce1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (212120). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Redis

Version

• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 6.2.11
• 6.2.12
• 6.2.13
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8
• 7.0.9
• 7.0.10
• 7.0.11
• 7.0.12
• 7.0.13
• 7.2.0
• 7.2.1

License

• open-source

Website

• Product: https://github.com/redis/redis/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion