basicsecurity.net
Proof, not just disclosure.
Threats / Red Hat / CVE-2018-14667
CVE-2018-14667 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-283EPSS 0.74171 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-09-28).
CISA KEV ↗Confirmed
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
Affected: Red Hat, JBoss RichFaces Framework. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-94 · Code InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by redhat (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by redhatCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.