Summary
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.apache.tomcat:tomcat to 7.0.7 or later; org.apache.tomcat:tomcat to 6.0.32 or later; org.apache.tomcat:tomcat to 5.5.33 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2010-4476? CVE-2010-4476 is a medium-severity security vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 7.0.0, < 7.0.7. It is fixed in 7.0.7, 6.0.32, 5.5.33.
- Which versions of org.apache.tomcat:tomcat are affected by CVE-2010-4476? org.apache.tomcat:tomcat (maven) versions >= 7.0.0, < 7.0.7 is affected.
- Is there a fix for CVE-2010-4476? Yes. CVE-2010-4476 is fixed in 7.0.7, 6.0.32, 5.5.33. Upgrade to this version or later.
- Is CVE-2010-4476 exploitable, and should I be worried? Whether CVE-2010-4476 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2010-4476 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2010-4476?
- Upgrade
org.apache.tomcat:tomcatto 7.0.7 or later - Upgrade
org.apache.tomcat:tomcatto 6.0.32 or later - Upgrade
org.apache.tomcat:tomcatto 5.5.33 or later
- Upgrade