Skip to content
Fencer Intel
medium 6.8

CVE-2015-0279 json

JBoss RichFaces before 4.5.4 allows remote attackers to inject expression language (EL) expressions and execute arbitrary Java code via the…

published 11y ago modified 4mo ago also EUVD-2015-0292

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

Summary

JBoss RichFaces before 4.5.4 allows remote attackers to inject expression language (EL) expressions and execute arbitrary Java code via the do parameter.

Is CVE-2015-0279 in your stack? 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-2015-0279 updated cvss 6.8

RichFaces: Remote Command Execution via insufficient EL parameter sanitization

  • Red Hat JBoss Operations Network 3 wildfly wildfly Red Hat JBoss Portal 5 richfaces richfaces Red Hat JBoss Portal 6 richfaces richfaces Red Hat JBoss SOA Platform 5 widlfly widlfly
    affected: no fix available
  • Red Hat JBoss Web Framework Kit 2.7
    fixed: vendor fix RHSA-2015:0719
  • Red Hat JBoss Data Grid 6 wildfly wildfly Red Hat JBoss Enterprise Application Platform 5 richfaces richfaces Red Hat JBoss Enterprise Application Platform 6 wildfly wildfly
    not affected: vulnerable code not present

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

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

CVSS scores

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

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.