Bug 771283 (CVE-2011-5035) - CVE-2011-5035 GlassFish: hash table collisions CPU usage DoS (oCERT-2011-003)
Summary: CVE-2011-5035 GlassFish: hash table collisions CPU usage DoS (oCERT-2011-003)
Alias: CVE-2011-5035
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Whiteboard: impact=moderate,public=20111228,repor...
Depends On:
Blocks: hashdos, oCERT-2011-003
TreeView+ depends on / blocked
Reported: 2012-01-03 05:29 UTC by David Jorm
Modified: 2019-06-08 18:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-01-03 05:34:06 UTC

Attachments (Terms of Use)

Description David Jorm 2012-01-03 05:29:10 UTC
Julian Wälde and Alexander Klink reported a way to degrade performance of the Java HashMap and HashTable implementations by filling the hash table with keys with identical hash codes. See bug #750533 for details. This issue can be used to mount an efficient details of service attack against GlassFish application server. GlassFish parses HTTP request parameters and stores them in a hash table. A remote attacker could use this flaw to make the GlassFish java process use an excessive amount of CPU time by sending a POST request with a large number of parameters which hash to the same value.

Comment 1 David Jorm 2012-01-03 05:34:06 UTC

Not vulnerable. This issue affects the GlassFish Web Container component. This
component is not shipped with any Red Hat products. JBoss Web and Tomcat
provide the web container used in all JBoss products.

Comment 2 Tomas Hoger 2012-02-15 09:04:21 UTC
Note that this CVE was also used for the HttpServer class in the standard Java Class Library, which did not limit the number of HTTP headers read from HTTP requests and stored in the HashMap, hence allowing the hash collision to be triggered.  That issue is tracked via separate bug #788606.

Note You need to log in before you can comment on or make changes to this bug.