# CVE-2010-4007: Weak cryptography in n/a

> Remote attackers can modify encrypted View State via padding oracle attacks due to missing MAC, potentially bypassing security controls in Oracle Mojarra applications.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v49c-75x7-q86w

## What is CVE-2010-4007?

CVE-2010-4007 is a medium-severity vulnerability in n/a, published on 20 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Oracle Mojarra uses an encrypted View State without a Message Authentication Code (MAC), which makes it easier for remote attackers to perform successful modifications of the View State via a padding oracle attack, a related issue to CVE-2010-2057.

Weakness: CWE-310

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

It affects 1 product.


Products: Oracle Mojarra.

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

No fix has been published for CVE-2010-4007 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-4007 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5855](https://insights.sbomify.com/CVE-2013-5855/): Improper Neutralization of Input During Web Page Generation in Mojarra (medium 4.3)
- [CVE-2010-2087](https://insights.sbomify.com/CVE-2010-2087/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-2672](https://insights.sbomify.com/CVE-2012-2672/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4007 is a medium-severity vulnerability in n/a, published on 20 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4007 in the wild and no public exploit code.

Affected product: n/a. 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-4007/ (Markdown: https://insights.sbomify.com/CVE-2010-4007/index.md)
```

## Sources

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

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