CVE-2010-3864

What it is

Multiple race conditions in ssl/t1_lib.c in OpenSSL 0.9.8f through 0.9.8o, 1.0.0, and 1.0.0a, when multi-threading and internal caching are enabled on a TLS server, might allow remote attackers to execute arbitrary code via client data that triggers a heap-based buffer overflow, related to (1) the TLS server name extension and (2) elliptic curve cryptography.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

22.1% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2010-11-17 16:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 22.1% in the next 30 days (EPSS).
• Severity: 7.6 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2010-11-17 16:00 UTC

Last modified

2026-06-16 23:23 UTC

Exploit probability

22.1% · EPSS, next 30 days

Weakness

CWE-362 · Race condition

Record status

Modified

Affected

• OpenSSL 0.9.8f
• OpenSSL 0.9.8g
• OpenSSL 0.9.8h
• OpenSSL 0.9.8i
• OpenSSL 0.9.8j
• OpenSSL 0.9.8k
• OpenSSL 0.9.8l
• OpenSSL 0.9.8m

Attack profile CVSS 2.0 · 7.6

Attack vector

Network

Complexity

High

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2010-3864.md and follow it. Check whether this project is affected by CVE-2010-3864. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge