Skip to content
Fencer Intel
medium 5.3

CVE-2011-4461 json

Improper Input Validation in Jetty

published 2011-12-30 14 y ago modified 2026-06-16 4 mo ago also GHSA-qxp4-27vx-xmm3 , EUVD-2022-5062

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Jetty 8.1.0.RC2 and earlier 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.

Patch / fix

  • maven org.eclipse.jetty:jetty-server 8.1.0.RC4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4461 updated cvss 5.0

jetty: hash table collisions CPU usage DoS (oCERT-2011-003)

  • Red Hat Enterprise Linux 6 jetty-eclipse
    affected: no fix planned “Will not fix”
  • Red Hat Fuse ESB Enterprise 7.1.0
    fixed: vendor fix RHSA-2012:1604
  • Red Hat Fuse Management Console 7.1.0
    fixed: vendor fix RHSA-2012:1606
  • Red Hat Fuse MQ Enterprise 7.1.0
    fixed: vendor fix RHSA-2012:1605

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.92% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
maven org.eclipse.jetty:jetty-server
<8.1.0.RC4
8.1.0.RC4

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.