GHSA-gvgc-rxmh-5hvw CVE-2010-4476

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

Medium Maven

Severity: Medium; The publisher's own rating, not a CVSS score
Exploit chance (EPSS): 23.49%; Chance of exploitation in the next 30 days. Higher than 97.80% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: —; Not classified
Fix: 7.0.7; Upgrade org.apache.tomcat:tomcat to this version or later

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.

Apache Tomcat introduced workarounds to avoid being affected by this issue in versions 7.0.7, 6.0.32, and 5.5.33.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.apache.tomcat:tomcat	`>= 7.0.0, < 7.0.7`	`7.0.7`
org.apache.tomcat:tomcat	`>= 6.0.0, < 6.0.32`	`6.0.32`
org.apache.tomcat:tomcat	`>= 5.5.0, < 5.5.33`	`5.5.33`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.tomcat:tomcat Maven → `7.0.7`

maven

<dependency><groupId>org.apache.tomcat</groupId><artifactId>tomcat</artifactId><version>7.0.7</version></dependency>

gradle

implementation("org.apache.tomcat:tomcat:7.0.7")

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2010-4476

Packages

github.com/apache/tomcat

Timeline

May 14, 2022 Published
Feb 27, 2024 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-69r9-qgr7-g2wj Apache Tomcat Missing Encryption of Sensitive Data vulnerability	High Known exploited	Also affects org.apache.tomcat:tomcat
GHSA-h3x4-894j-xpx5 Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability	Critical	Also affects org.apache.tomcat:tomcat
GHSA-9xv2-5v5q-p794 Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability	Critical	Also affects org.apache.tomcat:tomcat
GHSA-gcx9-497g-6cp6 Apache Tomcat has an Improper Access Control, Incorrect Authorization vulnerability	Critical	Also affects org.apache.tomcat:tomcat
GHSA-5m62-pw8w-7w9f Apache Tomcat - Security constraints not correctly applied	Critical	Also affects org.apache.tomcat:tomcat
GHSA-9m89-8frq-c98c Apache Tomcat - AJP secret compared in non-constant time	Low	Also affects org.apache.tomcat:tomcat
GHSA-5mp6-jrq3-r938 Apache Tomcat: LockOutRealm treats user names as case-sensitive	High	Also affects org.apache.tomcat:tomcat
GHSA-h6fc-48rj-7qqh Apache Tomcat - Digest authenticator will authenticate any unknown user	Critical	Also affects org.apache.tomcat:tomcat

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor