LiveActive security incident?Get immediate response
CVE Record

CVE-2010-2939: Double free vulnerability in the ssl3_get_key_exchange function in the OpenSSL client (ssl/s3_clnt.c) in Op...

Double free vulnerability in the ssl3_get_key_exchange function in the OpenSSL client (ssl/s3_clnt.c) in OpenSSL 1.0.0a, 0.9.8, 0.9.7, and possibly other versions, when using ECDH, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted private key with an invalid prime. NOTE: some sources refer to this as a use-after-free issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2010-2939 is an old OpenSSL client memory-management flaw. A malicious or malformed ECDH-related key exchange could crash affected clients and, according to the CVE description, might allow arbitrary code execution in some contexts. The practical concern today is legacy or embedded software still carrying OpenSSL 1.0.0a, 0.9.8, or 0.9.7-era code. Exposure is most likely in unsupported operating systems, appliances, or statically linked applications using old OpenSSL client libraries. The provided CVE metadata lists vendor and product as n/a, so affected deployments must be confirmed through local package, binary, and vendor advisory review. Prioritize this where old OpenSSL remains in production, especially in appliances or unsupported systems. It is not flagged as known exploited in the provided bundle, but OpenSSL client crashes and possible code execution justify cleanup during legacy risk reduction. Mitigation focus: Inventory OpenSSL versions in operating systems, appliances, containers, and statically linked applications.; Upgrade affected OpenSSL packages according to the relevant vendor advisory.; Retire unsupported systems that still depend on OpenSSL 1.0.0a, 0.9.8, or 0.9.7..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2010-2939 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.