CVE-2023-45145
low-risk
Published 2023-10-18
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.
Do I need to act?
-
0.58% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
3
CVSS 3.6/10
Low
LOCAL
/ HIGH complexity
Affected Vendors
References (14)
Third Party Advisory
https://security.netapp.com/advisory/ntap-20231116-0014/
Third Party Advisory
https://security.netapp.com/advisory/ntap-20231116-0014/
24
/ 100
low-risk
Severity
9/34 · Low
Exploitability
2/34 · Minimal
Exposure
13/34 · Low