# Apache MyFaces Vulnerable to Path Traversal

Advisory record · `GHSA-gjfx-9wx3-j6r7`

- **Identifiers:** `GHSA-gjfx-9wx3-j6r7` · `CVE-2011-4367`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 13 May 2022
- **Updated:** 29 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2022, 01:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.myfaces.core:myfaces-impl` (Maven): affected `>=2.0.0, <2.0.12 || >=2.1.0, <2.1.6`; fixed in `2.0.12`, `2.1.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache MyFaces Core (org.apache.myfaces.core:myfaces-impl) versions 2.0.0 to before 2.0.12 and 2.1.0 to before 2.1.6 are vulnerable to directory traversal. A remote attacker can use crafted requests to the JSF resource handler to read arbitrary files on the server. Upgrade to 2.0.12 or 2.1.6, or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.34, the 98th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gjfx-9wx3-j6r7)

## Sources

- [GitHub Advisory Database: GHSA-gjfx-9wx3-j6r7](https://github.com/advisories/GHSA-gjfx-9wx3-j6r7)
- [OSV: GHSA-gjfx-9wx3-j6r7](https://osv.dev/vulnerability/GHSA-gjfx-9wx3-j6r7)
- <https://nvd.nist.gov/vuln/detail/CVE-2011-4367>
- <https://exchange.xforce.ibmcloud.com/vulnerabilities/73100>
- <https://web.archive.org/web/20120213042504/http://www.securityfocus.com/bid/51939>
- <http://mail-archives.apache.org/mod_mbox/myfaces-announce/201202.mbox/%3C4F33ED1F.4070007%40apache.org%3E>
- <http://seclists.org/fulldisclosure/2012/Feb/150>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gjfx-9wx3-j6r7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gjfx-9wx3-j6r7/>. Everything for agents: <https://agentprime.io/llms.txt>.
