medium
5
CWE
NVD-CWE-Other
Advisory Published
Advisory Published
Updated

CVE-2010-4476

First published: Thu Feb 17 2011(Updated: )

The `Double.parseDouble` method in Java Runtime Environment (JRE) in Oracle Java SE and Java for Business 6 Update 23 and earlier, 5.0 Update 27 and earlier, and 1.4.2_29 and earlier, as used in OpenJDK, Apache, JBossweb, and other products, allows remote attackers to cause a denial of service via a crafted string that triggers an infinite loop of estimations during conversion to a double-precision binary floating-point number, as demonstrated using 2.2250738585072012e-308. Apache Tomcat introduced workarounds to avoid being affected by this issue in versions 7.0.7, 6.0.32, and 5.5.33.

Credit: secalert_us@oracle.com secalert_us@oracle.com

Affected SoftwareAffected VersionHow to fix
maven/org.apache.tomcat:tomcat>=5.5.0<5.5.33
5.5.33
maven/org.apache.tomcat:tomcat>=6.0.0<6.0.32
6.0.32
maven/org.apache.tomcat:tomcat>=7.0.0<7.0.7
7.0.7
Sun JRE<=1.6.0
Sun JRE=1.6.0
Sun JRE=1.6.0-update_1
Sun JRE=1.6.0-update_10
Sun JRE=1.6.0-update_11
Sun JRE=1.6.0-update_12
Sun JRE=1.6.0-update_13
Sun JRE=1.6.0-update_14
Sun JRE=1.6.0-update_15
Sun JRE=1.6.0-update_16
Sun JRE=1.6.0-update_17
Sun JRE=1.6.0-update_18
Sun JRE=1.6.0-update_19
Sun JRE=1.6.0-update_2
Sun JRE=1.6.0-update_20
Sun JRE=1.6.0-update_21
Sun JRE=1.6.0-update_22
Sun JRE=1.6.0-update_3
Sun JRE=1.6.0-update_4
Sun JRE=1.6.0-update_5
Sun JRE=1.6.0-update_6
Sun JRE=1.6.0-update_7
OpenJDK<=1.6.0
OpenJDK=1.6.0
OpenJDK=1.6.0-update_10
OpenJDK=1.6.0-update_11
OpenJDK=1.6.0-update_12
OpenJDK=1.6.0-update_13
OpenJDK=1.6.0-update_14
OpenJDK=1.6.0-update_15
OpenJDK=1.6.0-update_16
OpenJDK=1.6.0-update_17
OpenJDK=1.6.0-update_18
OpenJDK=1.6.0-update_19
OpenJDK=1.6.0-update_20
OpenJDK=1.6.0-update_21
OpenJDK=1.6.0-update_22
OpenJDK=1.6.0-update_3
OpenJDK=1.6.0-update_4
OpenJDK=1.6.0-update_5
OpenJDK=1.6.0-update_6
OpenJDK=1.6.0-update_7
OpenJDK=1.6.0-update1
OpenJDK=1.6.0-update1_b06
OpenJDK=1.6.0-update2
OpenJDK<=1.5.0
OpenJDK=1.5.0
OpenJDK=1.5.0-update1
OpenJDK=1.5.0-update10
OpenJDK=1.5.0-update11
OpenJDK=1.5.0-update12
OpenJDK=1.5.0-update13
OpenJDK=1.5.0-update14
OpenJDK=1.5.0-update15
OpenJDK=1.5.0-update16
OpenJDK=1.5.0-update17
OpenJDK=1.5.0-update18
OpenJDK=1.5.0-update19
OpenJDK=1.5.0-update2
OpenJDK=1.5.0-update20
OpenJDK=1.5.0-update21
OpenJDK=1.5.0-update22
OpenJDK=1.5.0-update23
OpenJDK=1.5.0-update24
OpenJDK=1.5.0-update25
OpenJDK=1.5.0-update26
OpenJDK=1.5.0-update3
OpenJDK=1.5.0-update4
OpenJDK=1.5.0-update5
OpenJDK=1.5.0-update6
OpenJDK=1.5.0-update7
OpenJDK=1.5.0-update8
OpenJDK=1.5.0-update9
Sun SDK<=1.4.2_29
Sun SDK=1.4.2
Sun SDK=1.4.2_1
Sun SDK=1.4.2_02
Sun SDK=1.4.2_3
Sun SDK=1.4.2_4
Sun SDK=1.4.2_5
Sun SDK=1.4.2_6
Sun SDK=1.4.2_7
Sun SDK=1.4.2_8
Sun SDK=1.4.2_9
Sun SDK=1.4.2_10
Sun SDK=1.4.2_11
Sun SDK=1.4.2_12
Sun SDK=1.4.2_13
Sun SDK=1.4.2_14
Sun SDK=1.4.2_15
Sun SDK=1.4.2_16
Sun SDK=1.4.2_17
Sun SDK=1.4.2_18
Sun SDK=1.4.2_19
Sun SDK=1.4.2_20
Sun SDK=1.4.2_21
Sun SDK=1.4.2_22
Sun SDK=1.4.2_23
Sun SDK=1.4.2_24
Sun SDK=1.4.2_25
Sun SDK=1.4.2_26
Sun SDK=1.4.2_27
Sun SDK=1.4.2_28
Sun JRE<=1.5.0
Sun JRE=1.5.0
Sun JRE=1.5.0-update1
Sun JRE=1.5.0-update10
Sun JRE=1.5.0-update11
Sun JRE=1.5.0-update12
Sun JRE=1.5.0-update13
Sun JRE=1.5.0-update14
Sun JRE=1.5.0-update15
Sun JRE=1.5.0-update16
Sun JRE=1.5.0-update17
Sun JRE=1.5.0-update18
Sun JRE=1.5.0-update19
Sun JRE=1.5.0-update2
Sun JRE=1.5.0-update20
Sun JRE=1.5.0-update21
Sun JRE=1.5.0-update22
Sun JRE=1.5.0-update23
Sun JRE=1.5.0-update24
Sun JRE=1.5.0-update25
Sun JRE=1.5.0-update26
Sun JRE=1.5.0-update3
Sun JRE=1.5.0-update4
Sun JRE=1.5.0-update5
Sun JRE=1.5.0-update6
Sun JRE=1.5.0-update7
Sun JRE=1.5.0-update8
Sun JRE=1.5.0-update9
Sun JRE<=1.4.2_29
Sun JRE=1.4.2
Sun JRE=1.4.2_1
Sun JRE=1.4.2_2
Sun JRE=1.4.2_3
Sun JRE=1.4.2_4
Sun JRE=1.4.2_5
Sun JRE=1.4.2_6
Sun JRE=1.4.2_7
Sun JRE=1.4.2_8
Sun JRE=1.4.2_9
Sun JRE=1.4.2_10
Sun JRE=1.4.2_11
Sun JRE=1.4.2_12
Sun JRE=1.4.2_13
Sun JRE=1.4.2_14
Sun JRE=1.4.2_15
Sun JRE=1.4.2_16
Sun JRE=1.4.2_17
Sun JRE=1.4.2_18
Sun JRE=1.4.2_19
Sun JRE=1.4.2_20
Sun JRE=1.4.2_21
Sun JRE=1.4.2_22
Sun JRE=1.4.2_23
Sun JRE=1.4.2_24
Sun JRE=1.4.2_25
Sun JRE=1.4.2_26
Sun JRE=1.4.2_27
Sun JRE=1.4.2_28

Remedy

http://www.oracle.com/technetwork/topics/security/alert-cve-2010-4476-305811.html

Remedy

http://www.oracle.com/technetwork/topics/security/cpuapr2011-301950.html

Remedy

http://www.oracle.com/technetwork/topics/security/javacpufeb2011-304611.html

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-4476?

    CVE-2010-4476 has a high severity rating due to its potential to cause a denial of service.

  • How do I fix CVE-2010-4476?

    To fix CVE-2010-4476, ensure that you update to Oracle Java SE 6 Update 24 or later, or apply the recommended patches for affected versions.

  • Which software is affected by CVE-2010-4476?

    CVE-2010-4476 affects multiple versions of the Java Runtime Environment including Oracle Java SE 6 Update 23 and earlier, and related software like Apache Tomcat.

  • Can CVE-2010-4476 be exploited remotely?

    Yes, CVE-2010-4476 can be exploited remotely, allowing attackers to cause a denial of service on vulnerable systems.

  • What products utilize the vulnerable method in CVE-2010-4476?

    The vulnerable `Double.parseDouble` method in CVE-2010-4476 is utilized by various products including OpenJDK, JBossweb, and Oracle's Java SE.

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