dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Jun 2022.
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2010-1871

HIGH · 8.8 CVSS v3.1 Published 2010-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JBoss Seam 2 fails to properly sanitize user inputs containing Expression Language (EL) syntax, allowing attackers to inject and execute arbitrary Java code via crafted URLs. This EL injection vulnerability permits remote code execution on the underlying system.

MitigationConfigure the Java Security Manager properly to enforce security policies that block unauthorized EL expression execution; alternatively, upgrade to a patched version of JBoss Seam/JBoss EAP if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss Enterprise Application PlatformApplication
Affected:= 4.3.0
Oncommand BalanceApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions
Oncommand Unified ManagerApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JBoss Seam 2 installation
    Search for seam*.jar files in the application deployment directory or check the application manifest for Seam 2 dependencies
    Affected if JBoss Seam 2 is present in the deployment
  2. Check JBoss EAP version
    Run 'jboss-admin.sh' or check version.txt in the JBoss installation directory, or inspect the server startup logs for the exact EAP version number
    Affected if The installed version is Red Hat JBoss Enterprise Application Platform 4.3.0
  3. Check NetApp OnCommand product installations
    Identify any installed Netapp Oncommand Balance, Oncommand Insight, or Oncommand Unified Manager instances in the environment
    Affected if Any version of these NetApp products is installed (they are all affected)
  4. Verify Java Security Manager configuration
    Check if the Java Security Manager is enabled by looking for -security flag in startup scripts or checking the conf/login-config.xml policy file
    Affected if Java Security Manager is not properly configured or is disabled

A user is affected if they run JBoss Seam 2 or JBoss EAP 4.3.0 or any NetApp OnCommand product without a properly configured Java Security Manager, allowing EL injection via crafted URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the Java Security Manager properly to enforce security policies that block unauthorized EL expression execution; alternatively, upgrade to a patched version of JBoss Seam/JBoss EAP if available.

Recommended fix Moderate confidence

JBoss Enterprise Application Platform 5.x or later with JBoss Seam 2.2.1+ (consult Red Hat for specific compatible versions)

  1. Ensure the Java Security Manager is properly configured for the JBoss application. Review and enforce the security policy files to restrict EL expression evaluation.
  2. If Java Security Manager configuration is not feasible, consider upgrading to a JBoss Enterprise Application Platform version that includes a fixed JBoss Seam 2 release ( Seam 2.2.1 or later).
  3. For Oncommand products (Balance, Insight, Unified Manager), contact the vendor (NetApp) for specific patches or upgrade paths, as these products bundle the vulnerable JBoss Seam component.
  4. Implement web application firewall (WAF) rules to filter suspicious patterns in URL parameters that may contain EL expressions (e.g., ${, #{, etc.).
Caveat Upgrading JBoss EAP may require application compatibility testing; verify application functionality after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jboss Enterprise Application Platform Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-1871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-1871 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data