Changes for page Engine_XalanJ

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,26 +5,23 @@
1		-{{toc/}}
2		-
3		-= Introduction =
4		-
5	5	[[Xalan-J>>http://xml.apache.org/xalan-j/||rel="__blank" title="Xalan-J Home Page"]] is a Java based XSLT engine by the Apache Project.
6	6
7		-= Supported version =
8	8
	4	+== Supported version ==
	5	+
9	9	1.0
10	10
11		-= Command line =
	8	+== Command line ==
12	12
13	13	$> java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl
14	14
15	15	__Note__ : xml-apis.jar, xercesImpl.jar and xalan*.jar must be in the $CLASSPATH
16	16
17		-= Identification strings =
	14	+== Identification strings ==
18	18
19	19	|=xsl:vendor-url|http:~/~/xml.apache.org/xalan-j
20	20	|=xsl:vendor|Apache Software Foundation
21	21	|=xsl:version|1.0
22	22
23		-= Special features =
	20	+== Special features ==
24	24
25	25	* Java properties disclosure
26	26	* Java environment disclosure
...	...	@@ -29,7 +29,7 @@
29	29	* File creation
30	30	* JDBC connectivity
31	31
32		-= Java properties disclosure =
	29	+== Java properties disclosure ==
33	33
34	34	The xsl:system-property() standard function can be called with non standard arguments, mapped to Java properties. In this example, the name of the Java properties is stored in a separate XML file ([[properties.xml>>attach:properties.xml]]). The XSLT code will, for each property, display its name and its value.
35	35
...	...	@@ -36,7 +36,7 @@
36	36	|=Namespace|=Function|=PoC|=Sample output
37	37	|http:~/~/www.w3.org/1999/XSL/Transform|system-property()|[[xalanj-java-properties.xsl>>attach:xalanj-java-properties.xsl]]|[[xalanj-java-properties-output.txt>>attach:xalanj-java-properties-output.txt]]
38	38
39		-= Java environment disclosure =
	36	+== Java environment disclosure ==
40	40
41	41	The checkEnvironment() extension function (documented [[here>>http://xml.apache.org/xalan-j/faq.html#faq-N10064||rel="__blank"]]) will display some information about the execution context (including available packages, paths, versions, ...).
42	42
...	...	@@ -43,7 +43,7 @@
43	43	|=Namespace|=Extension function|=PoC|=Sample output
44	44	|http:~/~/xml.apache.org/xalan|checkEnvironment()|[[xalanj-checkenv.xsl>>attach:xalanj-checkenv.xsl]]|[[xalanj-checkenv-output.txt>>attach:xalanj-checkenv-output.txt]]
45	45
46		-= Java code execution =
	43	+== Java code execution ==
47	47
48	48	The attached code will display the current date using a newly created "java.util.Date" object. This should be enough to demonstrate Java code execution.
49	49
...	...	@@ -51,11 +51,11 @@
51	51	|http:~/~/xml.apache.org/xalan/java/java.util.Date|new()|[[xalanj-java-date.xsl>>attach:xalanj-java-date.xsl]]|Current date:
52	52	Wed Jan 11 22:45:07 CET 2012
53	53
54		-= OS command execution =
	51	+== OS command execution ==
55	55
56	56	Once Java code execution is possible, it is trivial to execute arbitrary OS commands using the java.lang.Runtime class.
57	57
58		-== Command without output ==
	55	+=== Command without output ===
59	59
60	60	The attached PoC will not read the output of the executed command (because loops are hard in XSLT). But this is not a problem if a reverse-shell have already been started, isn't it ;-)
61	61
...	...	@@ -64,7 +64,7 @@
64	64
65	65	__Note__ : as arrays are not a native type in XSLT, we create one in Java via split() before passing it as an argument to [[exec(String[] cmdarray)>>http://docs.oracle.com/javase/1.4.2/docs/api/java/lang/Runtime.html#exec(java.lang.String[])||rel="__blank"]].
66	66
67		-== Reading stdout ==
	64	+=== Reading stdout ===
68	68
69	69	As the output have an unknown number of lines, we must use a __loop__ construct like "while" ... which is not available in XSLT. This limitation is due to the functional programming paradigm but can be circumvented using templates and recursion. This way, we can also __update__ some variables, but the syntax is awful and error prone.
70	70
...	...	@@ -77,11 +77,11 @@
77	77
78	78	It is of course possible to include commands for multiples OS in one file and to execute only the relevant ones.
79	79
80		-= Pure Java reverse-shell =
	77	+=== A pure Java reverse-shell ===
81	81
82	82	It is afaik not possible to get a pure Java reverse-shell, as we can't create threads :-(
83	83
84		-= File creation =
	81	+== File creation ==
85	85
86	86	The "write" extension element allows to create files on the engine side. The content written to the file must be valid UTF-8 (so plain ASCII works too). Existing files can be overwritten.
87	87
...	...	@@ -88,11 +88,11 @@
88	88	|=Namespace|=Extension element|=Parameter|=PoC
89	89	|http:~/~/xml.apache.org/xalan/redirect|write|file|[[xalanj-write.xsl>>attach:xalanj-write.xsl]]
90	90
91		-= JDBC connectivity =
	88	+== JDBC connectivity ==
92	92
93	93	It is possible to use XSLT to connect to any database having a corresponding installed JDBC driver.
94	94
95		-== Simple connection ==
	92	+=== Simple connection ===
96	96
97	97	The [[xalanj-jdbc-query.xsl>>attach:xalanj-jdbc-query.xsl]] PoC simply connects to a local MySQL database using some hard-coded credentials, executes a query and displays the result.
98	98
...	...	@@ -99,7 +99,7 @@
99	99	|=Namespace|=Extension function|=PoC
100	100	|org.apache.xalan.lib.sql.XConnection|new(), query() and close()|[[xalanj-jdbc-query.xsl>>attach:xalanj-jdbc-query.xsl]]
101	101
102		-== Credentials brute-forcing ==
	99	+=== Credentials brute-forcing ===
103	103
104	104	The [[xalanj-jdbc-bruteforce.xsl>>attach:xalanj-jdbc-bruteforce.xsl]] file will read some tuples (JDBC driver, database URL, username, passsword) from a XML file ([[xalanj-jdbc-bruteforce.xml>>attach:xalanj-jdbc-bruteforce.xml]]) and try to login with each one, effectively brute-forcing credentials from the engine side (usually on the backend ;-).
105	105