CVE-2010-1871

KEVRed Hat Linux JBoss Seam 2 Remote Code Execution Vulnerability

Description

JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, allows attackers to perform remote code execution. This vulnerability can only be exploited when the Java Security Manager is not properly configured.

JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for JBoss Expression Language (EL) expressions, which allows remote attackers to execute arbitrary code via a crafted URL. NOTE: this is only a vulnerability when the Java Security Manager is not properly configured.

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

PublishedAug 5, 2010

Last modifiedJun 16, 2026

Added to KEVDec 10, 2021

Remediation dueJun 10, 2022

References

archives.neohapsis.com/archives/bugtraq/2013-05/0117.htmlBroken Link
redhat.com/support/errata/RHSA-2010-0564.htmlBroken Link
securityfocus.com/bid/41994Broken LinkThird Party Advisory
securitytracker.com/id?1024253Broken LinkThird Party Advisory
vupen.com/english/advisories/2010/1929Broken LinkVendor Advisory
bugzilla.redhat.com/show_bug.cgi?id=615956Issue Tracking
exchange.xforce.ibmcloud.com/vulnerabilities/60794Third Party AdvisoryVDB Entry
security.netapp.com/advisory/ntap-20161017-0001/Third Party Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2010-1871US 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 1600 days
CVSS: 8.8 HIGH
EPSS (30-day exploit probability): 83.4% · top 1% of all CVEs
Weakness: CWE-917
Attack vector: Network, remotely reachable

Recommended actions

1.Apply updates per vendor instructions.
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.