| Reporter | Title | Published | Views | Family All 14 |
|---|---|---|---|---|
| CVE-2011-4367 | 9 Feb 201200:00 | – | circl | |
| CVE-2011-4367 | 19 Jun 201414:00 | – | cve | |
| CVE-2011-4367 | 19 Jun 201414:00 | – | cvelist | |
| CVE-2011-4367 | 19 Jun 201414:00 | – | debiancve | |
| Apache MyFaces Vulnerable to Path Traversal | 13 May 202201:24 | – | github | |
| CVE-2011-4367 | 19 Jun 201414:55 | – | nvd | |
| GHSA-GJFX-9WX3-J6R7 Apache MyFaces Vulnerable to Path Traversal | 13 May 202201:24 | – | osv | |
| Directory traversal | 19 Jun 201414:55 | – | prion | |
| CVE-2011-4367 | 5 Aug 202009:14 | – | redhatcve | |
| [SECURITY] CVE-2011-4367 Apache MyFaces information disclosure vulnerability | 12 Feb 201200:00 | – | securityvulns |
`--------------------------------------------------------------------------------------------------
CVE-2011-4367: Apache MyFaces information disclosure vulnerability
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
MyFaces Core 2.0.1 to 2.0.11
MyFaces Core 2.1.0 to 2.1.5
Earlier versions are not affected
Description:
MyFaces JavaServer Faces (JSF) allows relative paths in the
javax.faces.resource 'ln' parameter or writing the url so the resource
name include '..' sequences . An attacker could use the security
vulnerability to view files that they should not be able to.
Mitigation:
Users of affected versions should apply one of the following mitigations:
MyFaces Core 2.0.x users should update to 2.0.12
MyFaces Core 2.1.x users should update to 2.1.6
Example:
In linux or similar systems:
http://<hostname>:<port>/<context-root>/faces/javax.faces.resource/web.xml?ln=../WEB-INF
http://<hostname>:<port>/<context-root>/faces/javax.faces.resource/../WEB-INF/web.xml
or in windows systems:
http://<hostname>:<port>/<context-root>/faces/javax.faces.resource/web.xml?ln=..\\WEB-INF
http://<hostname>:<port>/<context-root>/faces/javax.faces.resource/..\\WEB-INF/web.xml
The 'ln' parameter should not allow a relative path. In the above example
the contents of the web.xml are displayed in the response to the attacker.
The part of the url that derive the resource name should not allow '..' as
valid char sequence.
Credit: Issue reported by Paul Nicolucci thanks to the security team at IBM
References:
--------------------------------------------------------------------------------------------------
regards,
Leonardo Uribe
`
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation