high
7.5
CWE
287
Advisory Published
CVE Published
Updated

CVE-2010-4252

First published: Thu Dec 02 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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
OpenSSL=0.9.7-beta5
OpenSSL=0.9.7-beta3
OpenSSL=0.9.5a-beta2
OpenSSL=0.9.7-beta6
OpenSSL=0.9.8b
OpenSSL=0.9.7l
OpenSSL=0.9.6i
OpenSSL=0.9.8m
OpenSSL=0.9.3
OpenSSL=0.9.8c
OpenSSL=0.9.7-beta2
OpenSSL=0.9.7c
OpenSSL=1.0.0-beta1
OpenSSL=0.9.5-beta1
OpenSSL=0.9.8n
OpenSSL<=1.0.0b
OpenSSL=1.0.0-beta2
OpenSSL=0.9.8p
OpenSSL=0.9.6d
OpenSSL=0.9.1c
OpenSSL=0.9.6
OpenSSL=0.9.7j
OpenSSL=0.9.6a
OpenSSL=0.9.8e
OpenSSL=0.9.4
OpenSSL=0.9.8g
OpenSSL=0.9.6a-beta2
OpenSSL=0.9.8k
OpenSSL=0.9.8d
OpenSSL=0.9.5a
OpenSSL=1.0.0-beta3
OpenSSL=0.9.6f
OpenSSL=0.9.8j
OpenSSL=0.9.6-beta3
OpenSSL=0.9.6l
OpenSSL=0.9.7k
OpenSSL=0.9.7g
OpenSSL=0.9.6e
OpenSSL=0.9.7d
OpenSSL=0.9.8l
OpenSSL=0.9.7
OpenSSL=0.9.6b
OpenSSL=0.9.7e
OpenSSL=0.9.7b
OpenSSL=0.9.6a-beta1
OpenSSL=1.0.0-beta4
OpenSSL=0.9.6k
OpenSSL=0.9.8a
OpenSSL=0.9.6g
OpenSSL=0.9.6-beta2
OpenSSL=0.9.7m
OpenSSL=0.9.7-beta4
OpenSSL=0.9.3a
OpenSSL=0.9.6h
OpenSSL=1.0.0
OpenSSL=0.9.7-beta1
OpenSSL=0.9.7i
OpenSSL=0.9.7h
OpenSSL=0.9.8o
OpenSSL=1.0.0-beta5
OpenSSL=0.9.6j
OpenSSL=0.9.8
OpenSSL=0.9.7a
OpenSSL=0.9.6c
OpenSSL=0.9.6-beta1
OpenSSL=0.9.6m
OpenSSL=0.9.8i
OpenSSL=0.9.8f
OpenSSL=0.9.5-beta2
OpenSSL=1.0.0a
OpenSSL=0.9.8h
OpenSSL=0.9.2b
OpenSSL=0.9.5
OpenSSL=0.9.5a-beta1
OpenSSL=0.9.6a-beta3
OpenSSL=0.9.7f

Remedy

http://cvs.openssl.org/chngview?cn=20098

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=659297

Remedy

https://github.com/seb-m/jpake

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203