CVE-2023-45145: Redis Unix-domain socket may have be exposed with the wrong permissions for a short time window.

Published Oct 18, 2023
·
Updated

CVE-2023-45145 - The wrong order of listen(2) and chmod(2) calls creates a race condition that can be used by another process to bypass desired Unix socket permissions on startup.

Upstream have released version 7.0.14/7.2.2 to fix CVE-2023-45145.

Reference: - https://github.com/redis/redis/releases/tag/7.0.14 - https://bugs.mageia.org/32406

Other sources

Redis could allow a local authenticated attacker to bypass security restrictions, caused by a race condition when a permissive umask(2) is used during startup. By sending a specially crafted request, an attacker could exploit this vulnerability to establish an unauthorized connection.

— IBM

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.

— Ubuntu

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

— Microsoft

Affected Software

21 affected componentsFixes available
debian/redis<=5:5.0.14-1+deb10u2, <=5:6.0.16-1+deb11u2
5:5.0.14-1+deb10u55:7.0.15-1~deb12u15:7.0.15-1
ubuntu/redis<5:4.0.9-1ubuntu0.2+
5:4.0.9-1ubuntu0.2+
ubuntu/redis<5:5.0.7-2ubuntu0.1+
5:5.0.7-2ubuntu0.1+
ubuntu/redis<5:6.0.16-1ubuntu1+
5:6.0.16-1ubuntu1+
ubuntu/redis<2:2.8.4-2ubuntu0.2+
2:2.8.4-2ubuntu0.2+
ubuntu/redis<7.2.2
7.2.2
ubuntu/redis<2:3.0.6-1ubuntu0.4+
2:3.0.6-1ubuntu0.4+
IBM Planning Analytics Local - IBM Planning Analytics Workspace<=2.1
IBM Planning Analytics Local - IBM Planning Analytics Workspace<=2.0
Redis redis>=2.6.0<6.2.14
Redis redis>=7.0.0<7.0.14
Redis redis>=7.2.0<7.2.2
Redis redis=2.6.0-rc1
Fedoraproject Fedora=37
Fedoraproject Fedora=38
Fedoraproject Fedora=39
Debian Debian Linux=10.0
redhat/redis<7.2.2
7.2.2
redhat/redis<7.0.14
7.0.14
redhat/redis<6.2.14
6.2.14
Microsoft cbl2 redis 6.2.14-1
Patch available

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/redis to a version that resolves this vulnerability.

    Fixed in 5:5.0.14-1+deb10u5Fixed in 5:7.0.15-1~deb12u1Fixed in 5:7.0.15-1
  2. Upgrade

    Upgrade ubuntu/redis to a version that resolves this vulnerability.

    Fixed in 5:4.0.9-1ubuntu0.2+
  3. Upgrade

    Upgrade ubuntu/redis to a version that resolves this vulnerability.

    Fixed in 5:5.0.7-2ubuntu0.1+
  4. Upgrade

    Upgrade ubuntu/redis to a version that resolves this vulnerability.

    Fixed in 5:6.0.16-1ubuntu1+
  5. Upgrade

    Upgrade ubuntu/redis to a version that resolves this vulnerability.

    Fixed in 2:2.8.4-2ubuntu0.2+
  6. Upgrade

    Upgrade ubuntu/redis to a version that resolves this vulnerability.

    Fixed in 7.2.2
  7. Upgrade

    Upgrade ubuntu/redis to a version that resolves this vulnerability.

    Fixed in 2:3.0.6-1ubuntu0.4+
  8. Upgrade

    Upgrade redhat/redis to a version that resolves this vulnerability.

    Fixed in 7.2.2
  9. Upgrade

    Upgrade redhat/redis to a version that resolves this vulnerability.

    Fixed in 7.0.14
  10. Upgrade

    Upgrade redhat/redis to a version that resolves this vulnerability.

    Fixed in 6.2.14
  11. Upgrade

    Upgrade redis to a version that resolves this vulnerability.

    Fixed in 7.2.2
  12. Upgrade

    Upgrade redis to a version that resolves this vulnerability.

    Fixed in 7.0.14
  13. Upgrade

    Upgrade redis to a version that resolves this vulnerability.

    Fixed in 6.2.14
  14. Compensating control

    If you cannot upgrade, work around CVE-2023-45145 by disabling Unix sockets in Redis (disable Unix-domain socket support).

  15. Compensating control

    If you cannot upgrade, start Redis with a restrictive umask during startup to avoid permissive umask race conditions that can expose the Unix socket with wrong permissions.

  16. Compensating control

    If you cannot upgrade, store the Redis Unix socket file in a protected directory to prevent other processes from creating an unauthorized connection during the startup window.

Event History

Oct 18, 2023
CVE Published
via Ubuntu·12:00 AM
CVE Published
via MITRE·08:17 PM
Data Sourced
via MITRE·08:17 PM
DescriptionSeverityWeakness
Data Sourced
09:15 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·10:31 PM
DescriptionSeverityAffected Software
Jan 12, 2024
Data Sourced
via Launchpad·12:25 AM
Description
Oct 1, 2025
Data Sourced
via Microsoft·11:11 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·11:11 PM
Affected Software
Updated
via Microsoft·11:11 PM
DescriptionSeverity

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-45145?

CVE-2023-45145 is a vulnerability in Redis where the Unix-domain socket may be exposed with the wrong permissions for a short time window.

2

What is Redis?

Redis is an in-memory database that persists on disk.

3

How does CVE-2023-45145 affect Redis?

CVE-2023-45145 affects Redis versions between 2.6.0 and 6.2.14, 7.0.0 and 7.0.14, and 7.2.0 and 7.2.2.

4

What is the severity of CVE-2023-45145?

The severity of CVE-2023-45145 is low, with a CVSS score of 3.6.

5

How can I fix CVE-2023-45145?

To fix CVE-2023-45145, upgrade Redis to a version that is not affected by the vulnerability.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203