CVE-2010-4252: High severity OpenSSL OpenSSL vulnerability

Q: What is the severity of CVE-2010-4252?

CVE-2010-4252 is considered a high severity vulnerability due to the potential for remote authentication bypass.

Q: What applications are affected by CVE-2010-4252?

CVE-2010-4252 affects OpenSSL versions prior to 1.0.0c, specifically those with J-PAKE enabled.

Q: How do I fix CVE-2010-4252?

To mitigate CVE-2010-4252, upgrade your OpenSSL version to 1.0.0c or later.

Q: What kind of attack can exploit CVE-2010-4252?

CVE-2010-4252 can be exploited through a crafted values attack in the J-PAKE protocol, allowing unauthorized authentication.

Q: Is there a workaround for CVE-2010-4252 if I cannot update OpenSSL immediately?

If you cannot update OpenSSL, consider disabling J-PAKE to reduce the risk of exploitation from CVE-2010-4252.

Published Dec 2, 2010

Updated

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.

Other sources

Sébastien Martini discovered a flaw in the OpenSSL's implementation of the J-PAKE authentication protocol. OpenSSL preformed insufficient validation of the public parameters received from the untrusted party, which could use this flaw to make J-PAKE protocol generate predictable session key. Hence an attacker could use this implementation flaw to successfully authenticate (i.e. prove knowledge of the shared secret) to the peer, usually server.

Sébastien Martini paper describing this flaw, as well as proof of concept code can be found in the following github repository: https://github.com/seb-m/jpake

OpenSSL upstream fix for the issue, which should be included in version 0.9.8q and 1.0.0c: http://cvs.openssl.org/chngview?cn=20098

Note: J-PAKE implementation is considered experimental upstream and is not enabled by default.

— Red Hat

Affected Software

76 affected components

OpenSSL OpenSSL=0.9.7-beta5

OpenSSL OpenSSL=0.9.7-beta3

OpenSSL OpenSSL=0.9.5a-beta2

OpenSSL OpenSSL=0.9.7-beta6

OpenSSL OpenSSL=0.9.8b

OpenSSL OpenSSL=0.9.7l

OpenSSL OpenSSL=0.9.6i

OpenSSL OpenSSL=0.9.8m

OpenSSL OpenSSL=0.9.3

OpenSSL OpenSSL=0.9.8c

OpenSSL OpenSSL=0.9.7-beta2

OpenSSL OpenSSL=0.9.7c

OpenSSL OpenSSL=1.0.0-beta1

OpenSSL OpenSSL=0.9.5-beta1

OpenSSL OpenSSL=0.9.8n

OpenSSL OpenSSL<=1.0.0b

OpenSSL OpenSSL=1.0.0-beta2

OpenSSL OpenSSL=0.9.8p

OpenSSL OpenSSL=0.9.6d

OpenSSL OpenSSL=0.9.1c

OpenSSL OpenSSL=0.9.6

OpenSSL OpenSSL=0.9.7j

OpenSSL OpenSSL=0.9.6a

OpenSSL OpenSSL=0.9.8e

OpenSSL OpenSSL=0.9.4

OpenSSL OpenSSL=0.9.8g

OpenSSL OpenSSL=0.9.6a-beta2

OpenSSL OpenSSL=0.9.8k

OpenSSL OpenSSL=0.9.8d

OpenSSL OpenSSL=0.9.5a

OpenSSL OpenSSL=1.0.0-beta3

OpenSSL OpenSSL=0.9.6f

OpenSSL OpenSSL=0.9.8j

OpenSSL OpenSSL=0.9.6-beta3

OpenSSL OpenSSL=0.9.6l

OpenSSL OpenSSL=0.9.7k

OpenSSL OpenSSL=0.9.7g

OpenSSL OpenSSL=0.9.6e

OpenSSL OpenSSL=0.9.7d

OpenSSL OpenSSL=0.9.8l

OpenSSL OpenSSL=0.9.7

OpenSSL OpenSSL=0.9.6b

OpenSSL OpenSSL=0.9.7e

OpenSSL OpenSSL=0.9.7b

OpenSSL OpenSSL=0.9.6a-beta1

OpenSSL OpenSSL=1.0.0-beta4

OpenSSL OpenSSL=0.9.6k

OpenSSL OpenSSL=0.9.8a

OpenSSL OpenSSL=0.9.6g

OpenSSL OpenSSL=0.9.6-beta2

OpenSSL OpenSSL=0.9.7m

OpenSSL OpenSSL=0.9.7-beta4

OpenSSL OpenSSL=0.9.3a

OpenSSL OpenSSL=0.9.6h

OpenSSL OpenSSL=1.0.0

OpenSSL OpenSSL=0.9.7-beta1

OpenSSL OpenSSL=0.9.7i

OpenSSL OpenSSL=0.9.7h

OpenSSL OpenSSL=0.9.8o

OpenSSL OpenSSL=1.0.0-beta5

OpenSSL OpenSSL=0.9.6j

OpenSSL OpenSSL=0.9.8

OpenSSL OpenSSL=0.9.7a

OpenSSL OpenSSL=0.9.6c

OpenSSL OpenSSL=0.9.6-beta1

OpenSSL OpenSSL=0.9.6m

OpenSSL OpenSSL=0.9.8i

OpenSSL OpenSSL=0.9.8f

OpenSSL OpenSSL=0.9.5-beta2

OpenSSL OpenSSL=1.0.0a

OpenSSL OpenSSL=0.9.8h

OpenSSL OpenSSL=0.9.2b

OpenSSL OpenSSL=0.9.5

OpenSSL OpenSSL=0.9.5a-beta1

OpenSSL OpenSSL=0.9.6a-beta3

OpenSSL OpenSSL=0.9.7f

Remediation

Event History

Dec 2, 2010

Data Sourced

via Red Hat·01:01 PM

DescriptionSeverityAffected Software

Dec 6, 2010

CVE Published

via MITRE·09:00 PM

Data Sourced

via MITRE·09:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2010-4252?

CVE-2010-4252 is considered a high severity vulnerability due to the potential for remote authentication bypass.

What applications are affected by CVE-2010-4252?

CVE-2010-4252 affects OpenSSL versions prior to 1.0.0c, specifically those with J-PAKE enabled.

How do I fix CVE-2010-4252?

To mitigate CVE-2010-4252, upgrade your OpenSSL version to 1.0.0c or later.

What kind of attack can exploit CVE-2010-4252?

CVE-2010-4252 can be exploited through a crafted values attack in the J-PAKE protocol, allowing unauthorized authentication.

Is there a workaround for CVE-2010-4252 if I cannot update OpenSSL immediately?

If you cannot update OpenSSL, consider disabling J-PAKE to reduce the risk of exploitation from CVE-2010-4252.

CVE-2010-4252: High severity OpenSSL OpenSSL vulnerability

Other sources

Affected Software

Remediation

Patch Available

Patch Available

Patch Available

Event History

Frequently Asked Questions

What is the severity of CVE-2010-4252?

What applications are affected by CVE-2010-4252?

How do I fix CVE-2010-4252?

What kind of attack can exploit CVE-2010-4252?

Is there a workaround for CVE-2010-4252 if I cannot update OpenSSL immediately?

Company

Resources

Contact