# CVE-2012-2672: Information disclosure in n/a

> Local attackers can access sensitive context information and resources from other web applications due to improper cleanup of FacesContext references.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2672, GHSA-78gp-c2rq-6jhr

## What is CVE-2012-2672?

CVE-2012-2672 is a low-severity vulnerability in n/a, published on 17 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Oracle Mojarra 2.1.7 does not properly "clean up" the FacesContext reference during startup, which allows local users to obtain context information an access resources from another WAR file by calling the FacesContext.getCurrentInstance function.

## Which versions are affected by CVE-2012-2672?

It affects 1 product.


Products: Oracle Mojarra.

## How do I fix CVE-2012-2672?

Upgrade to a fixed version.

## Is CVE-2012-2672 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4007](https://insights.sbomify.com/CVE-2010-4007/): Weak cryptography in n/a (medium 5.0)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2672 and fix it if it is affected.

What it is: CVE-2012-2672 is a low-severity vulnerability in n/a, published on 17 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2672 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-2012-2672/ (Markdown: https://insights.sbomify.com/CVE-2012-2672/index.md)
```

## Sources

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

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