CVE-2011-5035: n/a vulnerability

CVE-2011-5035: Oracle Glassfish 2.1.1, 3.0.1, and 3.1.1, as used in Communications Server 2.0, Sun Java System Application...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 00:23 UTC (UTC+00:00)

Security readout for executives and security teams

This vulnerability can let a remote attacker make affected Oracle GlassFish-based services waste CPU handling specially crafted form parameters. The expected impact is denial of service, not data theft or code execution. Business urgency depends on whether old GlassFish or bundled Sun/Oracle application server products remain exposed to untrusted traffic. Exposure is most likely in legacy Java web stacks running the named GlassFish or bundled application server versions, especially where form-handling endpoints accept traffic from untrusted users. The bundle says “possibly other products,” but does not prove additional affected products. Prioritize if legacy GlassFish-backed applications are internet-facing or business-critical. The impact is availability loss, so urgency is lower than remote code execution but higher for customer-facing portals, authentication flows, or revenue systems. Mitigation focus: Inventory GlassFish, Communications Server, and Sun Java System Application Server deployments.; Apply relevant Oracle CPU and downstream vendor advisories where they apply.; Retire or isolate unsupported affected versions exposed to untrusted traffic..

Prepared: Jun 27, 2026, 17:28 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-5035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 30, 2011, 01:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://github.com/FireFart/HashCollision-DOS-POC/blob/master/HashtablePOC.pyCVE reference · x_refsource_MISC
oval:org.mitre.oval:def:16908CVE reference · vdb-entry, signature

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.