CVE-2010-4252

CVE-2010-4252 is a high-severity vulnerability in Openssl with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-287.

Key facts

Description

OpenSSL before 1.0.0c, when J-PAKE is enabled, does not properly validate the public parameters in the J-PAKE protocol, which allows remote attackers to bypass the need for knowledge of the shared secret, and successfully authenticate, by sending crafted values in each round of the protocol.

Frequently asked questions

What is CVE-2010-4252?
OpenSSL before 1.0.0c, when J-PAKE is enabled, does not properly validate the public parameters in the J-PAKE protocol, which allows remote attackers to bypass the need for knowledge of the shared secret, and successfully authenticate, by sending crafted values in each round of the protocol.
How severe is CVE-2010-4252?
CVE-2010-4252 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2010-4252 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 8% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-4252?
CVE-2010-4252 primarily affects Openssl. In total, 76 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-4252?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2010-4252 published?
CVE-2010-4252 was published on 2010-12-06 and last updated on 2026-06-16.

References

Affected products (76)

More vulnerabilities in Openssl

All CVEs affecting Openssl →

Other CWE-287 (Improper Authentication) vulnerabilities

Browse all CWE-287 (Improper Authentication) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: