Skip to content
WatchlistMedium

CVE-2010-4476Jre Vulnerability

Apache Tomcat affected by infinite loop in Double.parseDouble method in Java Runtime Environment

Published May 14, 2022 · Updated Mar 9, 2026 · Also known as DEBIAN-CVE-2010-4476, DSA-2161-1, DSA-2161-2, GHSA-gvgc-rxmh-5hvw

Key Facts

Routine patching
  • CVE-2010-4476 is a medium-severity vulnerability (CVSS 5.0 v2) affecting Jdk (Sun), Jre (Sun), Sdk (Sun) and 22 more products.
  • It is not listed in any known-exploited vulnerabilities catalog. A public exploit is reported by tracking sources, but no code link is listed yet.
  • EPSS estimates a 23% probability of exploitation in the next 30 days.
  • Fixed versions are available, including java 1.4.2-ibm-0:1.4.2.13.8-1jpp.4.el4, java 1.5.0-ibm-1:1.5.0.12.3-1jpp.3.el6, java 1.6.0-ibm-1:1.6.0.9.1-1jpp.1.el5.
  • Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Scores

CVSS v2

5.0

AV:N/AC:L/Au:N/C:N/I:N/A:P

EPSS (30-day exploit likelihood)

23%

Higher than 97.7% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

34/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Advisories And Exploit References

Description

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.

Affected Products

204 affected entries in total
ProductAffected versionsFixed in
JdkSun1.5.0, 1.5.0-update1, 1.5.0-update10, 1.5.0-update11, 1.5.0-update12, 1.5.0-update13, 1.5.0-update14, 1.5.0-update151.6.0
JreSun1.4.2, 1.4.2_1, 1.4.2_10, 1.4.2_11, 1.4.2_12, 1.4.2_13, 1.4.2_14, 1.4.2_151.4.2_29
SdkSun1.4.2, 1.4.2_02, 1.4.2_1, 1.4.2_10, 1.4.2_11, 1.4.2_12, 1.4.2_13, 1.4.2_141.4.2_29
openjdk-6debianSee advisory6b18-1.8.3-2+squeeze1
org.apache.tomcat:tomcatmaven>= 7.0.05.5.33
20 more affected products in the full CVE brief

Patched Releases

java

1.4.2-ibm-0:1.4.2.13.8-1jpp.4.el4, 1.5.0-ibm-1:1.5.0.12.3-1jpp.3.el6, 1.6.0-ibm-1:1.6.0.9.1-1jpp.1.el5

java-1.6.0-openjdk

1:1.6.0.0-1.18.b17.0.1.el5, 1:1.6.0.0-1.36.b17.el6_0

java-1.6.0-openjdk-demo

1:1.6.0.0-1.18.b17.0.1.el5, 1:1.6.0.0-1.36.b17.el6_0

java-1.6.0-openjdk-devel

1:1.6.0.0-1.18.b17.0.1.el5, 1:1.6.0.0-1.36.b17.el6_0

java-1.6.0-openjdk-javadoc

1:1.6.0.0-1.18.b17.0.1.el5, 1:1.6.0.0-1.36.b17.el6_0

java-1.6.0-openjdk-src

1:1.6.0.0-1.18.b17.0.1.el5, 1:1.6.0.0-1.36.b17.el6_0

jbossweb

0:2.0.0-8.CP15.patch01.0jpp.ep1.1.el5, 0:2.1.10-5.patch01.1.ep5.el4

openjdk-6

6b18-1.8.3-2+squeeze1, 6b18-1.8.3-2~lenny1

org.apache.tomcat:tomcat

5.5.33, 6.0.32, 7.0.7

Jdk

1.5.0, 1.6.0

Jre

1.4.2_29, 1.5.0, 1.6.0

Sdk

1.4.2_29

tomcat5

0:5.5.28-12_patch_03.ep5.el5, 0:5.5.28-18_patch_03.ep5.el4, 5.5.23-0jpp.17.el5_6

tomcat5-admin-webapps

5.5.23-0jpp.17.el5_6

tomcat5-common-lib

5.5.23-0jpp.17.el5_6

tomcat5-jasper

5.5.23-0jpp.17.el5_6

tomcat5-jasper-javadoc

5.5.23-0jpp.17.el5_6

tomcat5-jsp-2.0-api

5.5.23-0jpp.17.el5_6

tomcat5-jsp-2.0-api-javadoc

5.5.23-0jpp.17.el5_6

tomcat5-server-lib

5.5.23-0jpp.17.el5_6

tomcat5-servlet-2.4-api

5.5.23-0jpp.17.el5_6

tomcat5-servlet-2.4-api-javadoc

5.5.23-0jpp.17.el5_6

tomcat5-webapps

5.5.23-0jpp.17.el5_6

tomcat6

0:6.0.24-11.patch_03.ep5.el4, 0:6.0.24-11.patch_03.ep5.el5, 0:6.0.24-24.el6_0, 6.0.24-24.el6_0

tomcat6-admin-webapps

6.0.24-24.el6_0

Timeline

  1. Publicly disclosed

    May 14, 2022

  2. Last updated

    Mar 9, 2026

References

15 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2010-4476 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.