Advisory Published
Updated

REDHAT-BUG-750533

First published: Tue Nov 01 2011(Updated: )

Julian Wälde and Alexander Klink reported that the String.hashCode() hash function is not sufficiently collision resistant. hashCode() value is used in the implementations of HashMap and Hashtable classes: <a href="http://docs.oracle.com/javase/6/docs/api/java/util/HashMap.html">http://docs.oracle.com/javase/6/docs/api/java/util/HashMap.html</a> <a href="http://docs.oracle.com/javase/6/docs/api/java/util/Hashtable.html">http://docs.oracle.com/javase/6/docs/api/java/util/Hashtable.html</a> A specially-crafted set of keys could trigger hash function collisions, which can degrade performance of HashMap or Hashtable by changing hash table operations complexity from an expected/average O(1) to the worst case O(n). Reporters were able to find colliding strings efficiently using equivalent substrings and meet in the middle techniques. This problem can be used to start a denial of service attack against Java applications that use untrusted inputs as HashMap or Hashtable keys. An example of such application is web application server (such as tomcat, see <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - CVE-2011-4858 tomcat: hash table collisions CPU usage DoS (oCERT-2011-003)" href="show_bug.cgi?id=750521">bug #750521</a>) that may fill hash tables with data from HTTP request (such as GET or POST parameters). A remote attack could use that to make JVM use excessive amount of CPU time by sending a POST request with large amount of parameters which hash to the same value. This problem is similar to the issue that was previously reported for and fixed in e.g. perl: <a href="http://www.cs.rice.edu/~scrosby/hash/CrosbyWallach_UsenixSec2003.pdf">http://www.cs.rice.edu/~scrosby/hash/CrosbyWallach_UsenixSec2003.pdf</a>

Affected SoftwareAffected VersionHow to fix
Java
Tomcat

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.

Frequently Asked Questions

  • What is the severity of REDHAT-BUG-750533?

    The severity of REDHAT-BUG-750533 is considered to be medium due to inadequate collision resistance in the String.hashCode() function.

  • How does REDHAT-BUG-750533 affect my application?

    REDHAT-BUG-750533 can lead to performance degradation and potential denial of service due to increased collision rates in HashMap and Hashtable implementations.

  • How do I fix REDHAT-BUG-750533?

    To fix REDHAT-BUG-750533, you should update to the latest versions of Oracle Java or Apache Tomcat that address this vulnerability.

  • What products are affected by REDHAT-BUG-750533?

    Affected products include Oracle Java and Apache Tomcat, specifically versions that implement the String.hashCode() function.

  • Can REDHAT-BUG-750533 be exploited remotely?

    While REDHAT-BUG-750533 is primarily a performance issue, under specific circumstances, it could be exploited remotely to affect service availability.

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