CVE Vulnerabilities

CVE-2024-0397

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Published: Jun 17, 2024 | Modified: Apr 11, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
5 LOW
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Ubuntu
MEDIUM

A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Name Vendor Start Version End Version
Red Hat Enterprise Linux 9 RedHat python3.9-0:3.9.21-1.el9_5 *
Red Hat Enterprise Linux 9 RedHat python3.12-0:3.12.5-2.el9 *
Red Hat Enterprise Linux 9 RedHat python3.11-0:3.11.9-7.el9 *
Red Hat Enterprise Linux 9 RedHat python3.9-0:3.9.21-1.el9_5 *
Python2.7 Ubuntu focal *
Python2.7 Ubuntu trusty/esm *
Python3.10 Ubuntu jammy *
Python3.10 Ubuntu upstream *
Python3.11 Ubuntu mantic *
Python3.12 Ubuntu mantic *
Python3.12 Ubuntu upstream *
Python3.4 Ubuntu trusty/esm *
Python3.5 Ubuntu trusty/esm *
Python3.8 Ubuntu esm-infra/focal *
Python3.8 Ubuntu focal *
Python3.9 Ubuntu focal *

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
  • Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

References