CVE-2011-5035: Input Validation

Published Dec 30, 2011
·
Updated

Oracle Glassfish 2.1.1, 3.0.1, and 3.1.1, as used in Communications Server 2.0, Sun Java System Application Server 8.1 and 8.2, and possibly other products, computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters, aka Oracle security ticket S0104869.

Affected Software

3 affected components
Oracle GlassFish Server<=3.1.1
Oracle GlassFish Server=2.1.1
Oracle GlassFish Server=3.0.1

Event History

Dec 30, 2011
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-5035?

CVE-2011-5035 is classified as a high severity vulnerability due to its potential for allowing remote attackers to exploit hash collisions.

2

How do I fix CVE-2011-5035?

To mitigate CVE-2011-5035, you should upgrade to the latest version of Oracle GlassFish Server that is not affected, beyond version 3.1.1.

3

Which versions of Oracle GlassFish Server are affected by CVE-2011-5035?

CVE-2011-5035 affects Oracle GlassFish Server versions 2.1.1, 3.0.1, and 3.1.1.

4

Can CVE-2011-5035 be exploited remotely?

Yes, CVE-2011-5035 can be exploited remotely, allowing attackers to trigger predictable hash collisions.

5

What type of attack does CVE-2011-5035 facilitate?

CVE-2011-5035 facilitates collision-based attacks that can manipulate input parameters to execute malicious actions.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203