vciy

CVE-2024-0397

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Memory race condition in ssl.SSLContext certificate store methods

CVE-2024-03973 of 4 sources documented this
unranked

No rank

rank@v1 withholds a number for this record

nothing this rule scores is held for this record, so there is no ordering to state. That is a fact about the sources, not a finding about the software.

Hindsight · the state

0.0081EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2024-06-18, 757 days at 0.01, as of 2026-07-15. arc-rules@v1

Foresight · where to check next

Microsoft WindowsLinuxMicrosoft WindowsAndroidGoogle Chrome0397

This record is one instance of CWE-362, concurrent execution using shared resource with improper synchronization ('race condition'). The index holds 2680 prior instances of this class, 12 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Python Software Foundation CPython? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')receipt
Published consequencesCWE-362: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other); Availability: DoS: Crash, Exit, or Restart, DoS: Instability…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in3.8.20; 3.9.20; 3.10.14; 3.11.9; 3.12.3; 3.13.0a5receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.0081 · top 45% of all CVEsreceipt
Assigned byPSFreceipt
Recorded changes25 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productPython Software Foundation CPythonreceipt
Fixed in3.8.20; 3.9.20; 3.10.14; 3.11.9; 3.12.3; 3.13.0a5receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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

NVD's analysis a second authority

weakness
CWE-362
also scored by
7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

check it yourself github.com github.com mail.python.org github.com github.com github.com +4 morereceipt

Movement the material steps

18 Jun 20240.00044
17 Mar 20250.00789 · scoring model v2025.03.14
15 Jun 20260.00804 · scoring model v2026.06.15
15 Jul 20260.0081
Show all 25 observations
18 Jun 20240.00044
17 Mar 20250.00789
29 Mar 20250.01401
30 Mar 20250.00789
3 Apr 20250.00855
12 Apr 20250.00361
13 Apr 20250.00401
14 Apr 20250.00393
18 May 20250.00401
21 May 20250.00393
16 Jul 20250.00401
17 Jul 20250.00393
26 Jul 20250.00232
4 Aug 20250.00226
16 Aug 20250.00232
21 Aug 20250.00226
6 Nov 20250.00417
18 Nov 20250.01176
21 Nov 20250.00417
27 Dec 20250.00384
24 May 20260.0033
29 May 20260.00395
11 Jun 20260.00384
15 Jun 20260.00804
15 Jul 20260.0081

25 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.0081Published2024-06-17Index as of2026-07-15

The record had been public for 2 years when this index was last written.

Published 2024-06-17 receipt · Index as of 2026-07-15 derived

The pattern, elsewhere

This record is one instance of CWE-362, concurrent execution using shared resource with improper synchronization ('race condition'). The index holds 2680 prior instances of this class, 12 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2023-36884 · Microsoft Windows 10 Version 1507only 1 attribute comparableKEV listed · 2023receipt
CVE-2025-39964 · Linuxonly 1 attribute comparableKEV listed · 2025receipt
CVE-2025-62215 · Microsoft Windows 10 Version 1809only 1 attribute comparableKEV listed · 2025receipt
CVE-2022-26904 · Microsoft Windows 10 Version 1809only 1 attribute comparableKEV listed · 2022receipt
CVE-2021-0920 · Androidonly 1 attribute comparableKEV listed · 2021receipt
CVE-2021-21166 · Google Chromeonly 1 attribute comparableKEV listed · 2021receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

2680 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2024-0397.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.