ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-45145

Redis Unix-domain socket may be exposed with the wrong permissions for a short time window.

Published Oct 18, 2023 · catalog updated Jun 16, 2026 · Redis Unix-domain socket may

Last checked Oct 31, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2023-45145. EPSS is 0.44%. Act only if a listed version of Redis Unix-domain socket may is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Redis Unix-domain socket may).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Low3.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.44%
Remediation
Version ranges on file
Affected products
cpe debian/debian linux · cpe fedoraproject/fedora · cpe redis/redis · n/a redis-server

### Impact 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. The problem exists since Redis 2.6.0-RC1. ### Patches The problem is fixed in Redis 7.2.2, 7.0.14 or 6.2.14. ### Workaround 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. ### Credit The problem was reported by Alexander Aleksandrovič Klimov of Icinga.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe debian/debian linux10.0
  • cpe fedoraproject/fedora37
  • cpe redis/redis2.6.0
  • cpe redis/redis< 6.2.14
  • cpe redis/redis< 7.0.14
  • cpe redis/redis< 7.2.2
  • n/a redis-server>= 2.6.0-rc1

How to fix CVE-2023-45145

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2023-45145. EPSS is 0.44%. Act only if a listed version of Redis Unix-domain socket may is installed.

Which versions are affected?

Compare what you have installed with debian/debian linux 10.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-668: Exposure of Resource to Wrong Sphere. EPSS 0.44%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Redis security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 18, 2023 · Monitored products — high

    Detected

    CVE-2023-45145 is listed by Redis is an in-memory database that persists on disk..

  2. Jun 16, 2026 · Monitored products — high

    Updated

    CVE-2023-45145 is listed by Redis is an in-memory database that persists on disk..

Sources

  • FIRST EPSSExploitation probabilityCVE-2023-45145

    30-day exploitation probability 0.44%

    first.org
  • Maintainer security tabsVendor advisoryGHSA-ghmp-889m-7cvx

    ### Impact 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. The problem exists since Redis 2.6.0-RC1. ### Patches The problem is fixed in Redis 7.2.2, 7

    github.com
  • Monitored products — highVendor advisoryCVE-2023-45145

    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. T

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 31, 2026
  • Maintainer security tabsOct 31, 2026
  • Monitored products — highOct 31, 2026