# CVE-2010-1871: Red Hat Linux JBoss Seam 2 Remote Code Execution

> Remote attackers can execute arbitrary code via crafted URLs in JBoss Seam if the Java Security Manager is not properly configured.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 10 Dec 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Aug 2010
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-r6fv-qmrc-3h24, RHSA-2010:0564

## What is CVE-2010-1871?

CVE-2010-1871 is a high-severity code injection vulnerability in Netapp Oncommand Balance, published on 4 Aug 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement)

## Which versions are affected by CVE-2010-1871?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jboss-seam2` | Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | All versions | 0:2.0.2.FP-1.ep1.24.el4 |
| `jboss-seam2-docs` | Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | All versions | 0:2.0.2.FP-1.ep1.24.el4 |
| `jboss-seam2` | Red Hat:jboss_enterprise_application_platform:4.3.0::el5 | All versions | 0:2.0.2.FP-1.ep1.24.el5 |
| `jboss-seam2-docs` | Red Hat:jboss_enterprise_application_platform:4.3.0::el5 | All versions | 0:2.0.2.FP-1.ep1.24.el5 |

Products: Netapp Oncommand Balance, Netapp Oncommand Insight, Netapp Oncommand Unified Manager, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2010-1871?

Change a configuration setting. US federal agencies must fix it by 10 Jun 2022.

## Is CVE-2010-1871 being exploited?

Yes. Attackers have exploited CVE-2010-1871 in the wild since at least 10 Dec 2021.

Public exploit code:

- JBoss Seam 2 Remote Command Execution (metasploit)
- JBoss Seam 2 File Upload and Execute (metasploit)
- JBoss Seam 2 - Arbitrary File Upload / Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Netapp Oncommand Balance

- [CVE-2014-9353](https://insights.sbomify.com/CVE-2014-9353/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2014-9354](https://insights.sbomify.com/CVE-2014-9354/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1871 and fix it if it is affected.

What it is: CVE-2010-1871 is a high-severity code injection vulnerability in Netapp Oncommand Balance, published on 4 Aug 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2010-1871 in the wild since at least 10 Dec 2021.

Affected product: Netapp Oncommand Balance. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-1871/ (Markdown: https://insights.sbomify.com/CVE-2010-1871/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-1871
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-1871
- OSV: https://osv.dev/vulnerability/CVE-2010-1871

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-1871/
Summaries are generated and may contain mistakes; the official description above is the record.