Threats / Red Hat / CVE-2018-14667
CVE-2018-14667
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Red Hat JBoss RichFaces Framework vulnerability
Red Hat JBoss RichFaces Framework contains an expression language injection vulnerability in the UserResource component that allows remote, unauthenticated attackers to execute arbitrary code through malicious serialized Java objects.
Verdict
Today item — known-exploited.
A remote attacker can inject and execute arbitrary code without authentication by exploiting expression language evaluation in the UserResource resource handler, leveraging unsafe deserialization of crafted Java objects.
CISA KEV Yes · 2023-09-285EPSS 0.74171 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-09-28).
Probability (EPSS)
EPSS 0.74171 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Red Hat, JBoss RichFaces Framework. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1787 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious serialized Java object chain targeting the UserResource component.
Business
The organization runs vulnerable JBoss RichFaces instances exposed to the internet.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send the payload to the UserResource endpoint without requiring authentication.
Business
No authentication barrier exists to prevent exploitation of this code path.
3
Lateral reach — past segmentation narrative 3
Attacker
I trigger expression language injection during deserialization, executing arbitrary code on the server.
Business
The application server executes attacker-controlled code with full application privileges.
4
Data at risk — exfiltration narrative 4
Attacker
I establish persistence or pivot to internal systems from the compromised application server.
Business
The breach expands to backend infrastructure, databases, and connected systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05