How severe is CVE-2011-4367?

No CVSS score has been assigned to CVE-2011-4367 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-4367?

CVE-2011-4367 affects the following packages: org.apache.myfaces.core:myfaces-impl (Maven), org.apache.myfaces.core:myfaces-impl (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-4367?

Update org.apache.myfaces.core:myfaces-impl to 2.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4367 is resolved across your whole dependency graph.

How do I detect CVE-2011-4367 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.myfaces.core:myfaces-impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-4367 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2011-4367 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2011-4367, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-4367?

CVE-2011-4367 has an EPSS (Exploit Prediction Scoring System) score of 33.7%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2011-4367?

CVE-2011-4367 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2011-4367 published, and has it been updated?

CVE-2011-4367 was published on May 13, 2022 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2011-4367 — myfaces-impl

CVE-2011-4367 is a Path Traversal vulnerability in org.apache.myfaces.core:myfaces-impl. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.myfaces.core:myfaces-impl — see the affected versions and patch details below.

Apache MyFaces Vulnerable to Path Traversal

Published

May 13, 2022

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

4 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

33.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.myfaces.core:myfaces-impl☕org.apache.myfaces.core:myfaces-impl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Multiple directory traversal vulnerabilities in MyFaces JavaServer Faces (JSF) in Apache MyFaces Core 2.0.x before 2.0.12 and 2.1.x before 2.1.6 allow remote attackers to read arbitrary files via a .. (dot dot) in the (1) ln parameter to faces/javax.faces.resource/web.xml or (2) the PATH_INFO to faces/javax.faces.resource/.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.myfaces.core:myfaces-impl`	≥ 2.0.0&&< 2.0.12	2.0.12`org.apache.myfaces.core:myfaces-impl:2.0.12`
☕Maven	`org.apache.myfaces.core:myfaces-impl`	≥ 2.1.0&&< 2.1.6	2.1.6`org.apache.myfaces.core:myfaces-impl:2.1.6`

Affected Products

1 product · 2 configurations

Application

myfacesapache

≥ 2.1.0 && ≤ 2.1.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-36681remotemultiple✓ Verified

Apache MyFaces - 'ln' Information Disclosure

by Paul Nicolucci · Feb 9, 2012

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.myfaces.core:myfaces-impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.myfaces.core:myfaces-impl to 2.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4367 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Multiple directory traversal vulnerabilities in MyFaces JavaServer Faces (JSF) in Apache MyFaces Core 2.0.x before 2.0.12 and 2.1.x before 2.1.6 allow remote attackers to read arbitrary files via a `..` (dot dot) in the (1) ln parameter to `faces/javax.faces.resource/web.xml` or (2) the `PATH_INFO` to `faces/javax.faces.resource/`.

O3 Security · Impact-Aware SCA

Is CVE-2011-4367 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works