Threats / Red Hat / CVE-2010-1871
CVE-2010-1871
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Red Hat JBoss Seam 2 vulnerability
JBoss Seam 2 in Red Hat Enterprise Application Platform allows remote code execution when Java Security Manager is improperly configured, enabling attackers to execute arbitrary code on affected systems.
Verdict
Today item — known-exploited.
Remote code execution vulnerability in JBoss Seam 2 exploitable when Java Security Manager lacks proper configuration. High EPSS score and active exploitation in the wild indicate significant risk requiring immediate patching and security manager hardening.
CISA KEV Yes · 2021-12-104EPSS 0.83397 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module10
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports 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 2021-12-10).
Probability (EPSS)
EPSS 0.83397 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Red Hat, JBoss Seam 2. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · 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 4146 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.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 identify that the target runs JBoss Seam 2 with an improperly configured or disabled Java Security Manager.
Business
Attackers gain ability to execute arbitrary code with application privileges, potentially compromising data confidentiality, integrity, and system availability.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft and deliver a malicious request that exploits the input validation weakness to trigger code execution.
Business
Unauthorized code execution allows lateral movement within the network, installation of persistent backdoors, and exfiltration of sensitive business data.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence and escalate privileges to gain deeper system access.
Business
Compromise extends beyond the application to underlying infrastructure, enabling attackers to disrupt operations and access other critical 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