full-disclosure - [SECURITY] CVE-2011-4367 Apache MyFaces information disclosure vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Thu, 09 Feb 2012 10:54:42 -0500
From: Leonardo Uribe <lu4242@...che.org>
To: security@...che.org, full-disclosure@...ts.grok.org.uk, 
	bugtraq@...urityfocus.com
Subject: [SECURITY] CVE-2011-4367 Apache MyFaces
	information disclosure vulnerability

--------------------------------------------------------------------------------------------------

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

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/