CVE-2018-14667

KEVRed Hat JBoss RichFaces Framework Expression Language Injection Vulnerability

Description

Red Hat JBoss RichFaces Framework contains an expression language injection vulnerability via the UserResource resource. A remote, unauthenticated attacker could exploit this vulnerability to execute malicious code using a chain of Java serialized objects via org.ajax4jsf.resource.UserResource$UriData.

The RichFaces Framework 3.X through 3.3.4 is vulnerable to Expression Language (EL) injection via the UserResource resource. A remote, unauthenticated attacker could exploit this to execute arbitrary code using a chain of java serialized objects via org.ajax4jsf.resource.UserResource$UriData.

CVSS 3.1 vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

PublishedNov 6, 2018

Last modifiedJun 17, 2026

Added to KEVSep 28, 2023

Remediation dueOct 19, 2023

References

packetstormsecurity.com/files/156663/Richsploit-RichFaces-Exploitation-Toolkit.htmlThird Party AdvisoryVDB Entry
seclists.org/fulldisclosure/2020/Mar/21Mailing ListThird Party Advisory
securitytracker.com/id/1042037Third Party AdvisoryVDB Entry
access.redhat.com/errata/RHSA-2018:3517Vendor Advisory
access.redhat.com/errata/RHSA-2018:3518Vendor Advisory
access.redhat.com/errata/RHSA-2018:3519Vendor Advisory
access.redhat.com/errata/RHSA-2018:3581Vendor Advisory
bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14667Issue TrackingVendor Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-14667US Government Resource

0 recent articles mention this CVE

Risk assessment · Critical

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 1104 days
CVSS: 9.8 CRITICAL
EPSS (30-day exploit probability): 74.2% · top 1% of all CVEs
Weakness: CWE-94
Attack vector: Network, remotely reachable
Preconditions: No privileges and no user interaction

Recommended actions

1.Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.