CVE-2018-14667
Red Hat JBoss RichFaces Framework Expression Language Injection Vulnerability
Red Hat JBoss RichFaces Framework
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 28 September 2023. US federal agencies were required to remediate it by 19 October 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 74.2%, which is higher than 99.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2018-14667 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2018-14667.
What does CVE-2018-14667 affect?
CVE-2018-14667 affects Red Hat JBoss RichFaces Framework. 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.
How severe is CVE-2018-14667?
CVE-2018-14667 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 74.2%, higher than 99.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 19 October 2023.
How should organisations respond to CVE-2018-14667?
Apply the vendor patch for Red Hat JBoss RichFaces Framework as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.