Skip to content
Fencer Intel
medium 4.3

CVE-2014-0086 json

JBoss RichFaces Improper Input Validation vulnerability

published 12y ago modified 4mo ago also GHSA-xfxv-f945-4qv6 , EUVD-2022-5776

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

The doFilter function in webapp/PushHandlerFilter.java in JBoss RichFaces 4.3.4, 4.3.5, and 5.x allows remote attackers to cause a denial of service (memory consumption and out-of-memory error) via a large number of malformed atmosphere push requests.

Patch / fix

  • maven org.richfaces:richfaces 5.0.0.Alpha3

Is CVE-2014-0086 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2014-0086 updated cvss 4.3

RichFaces: remote denial of service via memory exhaustion

  • Red Hat JBoss Portal 6 richfaces richfaces
    affected: no fix available
  • Red Hat JBoss Portal 6.2
    fixed: vendor fix RHSA-2015:1009
  • Red Hat JBoss Web Framework Kit 2.5
    fixed: vendor fix RHSA-2014:0335

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

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

Exploits and checks

  • github.com https://github.com/pslegr/core-1/commit/8131f15003f5bec73d475d2b724472e4b87d0757 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected packages

ecosystem package affected fixed in
maven org.richfaces:richfaces
>=4.3.4, <=4.3.5
>=5.0.0.Alpha1, <5.0.0.Alpha3
5.0.0.Alpha3

Classification

Weakness
  • CWE-20 Improper Input Validation

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.