# CVE-2010-2086: Apache MyFaces Cross-site Scripting vulnerability

> Remote attackers can execute arbitrary code or XSS via modified serialized view objects in Apache MyFaces when unencrypted view state is enabled.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 May 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-92cv-wv2c-8899

## What is CVE-2010-2086?

CVE-2010-2086 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 May 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

Apache MyFaces 1.1.7 and 1.2.8, as used in IBM WebSphere Application Server and other applications, does not properly handle an unencrypted view state, which allows remote attackers to conduct cross-site scripting (XSS) attacks or execute arbitrary Expression Language (EL) statements via vectors that involve modifying the serialized view object.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

4 open source packages ship an affected version, including org.apache.myfaces.core:myfaces-core-module. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.myfaces.core:myfaces-core-module` | Maven | All versions to 1.1.7 | None |
| `org.apache.myfaces.core:myfaces-core-module` | Maven | All versions to 1.1.7 | None |
| `org.apache.myfaces.core:myfaces-core-module` | Maven | From 1.2.0 to 1.2.8 | None |
| `org.apache.myfaces.core:myfaces-core-module` | Maven | From 1.2.0 to 1.2.8 | None |

Products: Apache Myfaces.

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

Upgrade to a fixed version.

## Is CVE-2010-2086 being exploited?

There is no known exploitation of CVE-2010-2086 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-26296](https://insights.sbomify.com/CVE-2021-26296/): Cross-Site Request Forgery (CSRF) vulnerability in Apache MyFaces (high 7.5)
- [CVE-2011-4343](https://insights.sbomify.com/CVE-2011-4343/): Apache MyFaces Vulnerable to EL Injection (high 7.5)
- [CVE-2011-4367](https://insights.sbomify.com/CVE-2011-4367/): Apache MyFaces Vulnerable to Path Traversal (medium 5.0)
- [CVE-2010-2057](https://insights.sbomify.com/CVE-2010-2057/): Improper Authentication in Apache MyFaces (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2086 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 May 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: There is no known exploitation of CVE-2010-2086 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.myfaces.core:myfaces-core-module (Maven): affected all versions up to 1.1.7; no fix listed
- org.apache.myfaces.core:myfaces-core-module (Maven): affected all versions up to 1.1.7; no fix listed
- org.apache.myfaces.core:myfaces-core-module (Maven): affected from 1.2.0 up to 1.2.8; no fix listed
- org.apache.myfaces.core:myfaces-core-module (Maven): affected from 1.2.0 up to 1.2.8; no fix listed

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-2086/ (Markdown: https://insights.sbomify.com/CVE-2010-2086/index.md)
```

## Sources

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

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