Skip to main content

MHTML files

Today my colleague Surendra had a query regarding a weird popup coming up while he was trying to access a website. Although even, I was not very familiar with the kind of message he was getting. All we wanted to know, if it's really anything malicious! He was trying to access some page, and the website was making some weird request to the webserver in order to load some object (here it was a calender) from the server:

mhtml:http://abc.com/resources/Calnder.mht

The warning message was like this:

Even I had not noticed like anything in the past, I did a little research on the topic. The browser was trying to load some MHTML page.MHTML is simply a MIME HTML format, used to combine all the external resources, which are generally loaded as external link, with HTML code into a single file. Generally this file has extension as .mht. So any .mht file contains mix of HTML code and other objects such as, Flash, images, applets, audio files etc. The content of .mht file is encoded in base64. (Wiki)

So when you are requesting a .mht file it will be loaded into multipart one-by-one, as the file may be large. Also, to minimize the lots of GET requests to server, it can be used. So IE uses mhtml:http:// format to request such type of files from the server. But again IE strips the mhtml part and makes the normal GET request to the web server. Again when it gets the response from the server again it prefixes the mhtml before it. So for example, if you request mhtml://http://abc.com/anyFile.mht, IE interprets the mhtml request for multipart/related content and sends a normal GET request to the server as http://abc.com/anyFile.mht. After receiving the response back it again prefixes with mhtml as mhtml:http://abc.com/anyFile.mht.

So, regarding his case, there was some script injection vulnerability with the way the Windows treats the MHTML long ago. So, Microsoft came up with a lock-down solution for the MHTML being used in the URL. Now you can’t use mhtml in urls/hyperlinks if that fix is applied on the server. But still MHTML can works behind the scene, the only thing is you can never request it as mhtml:http://. Generally .mht doesn’t contain script but if it contains that and the lock-down for the MHTML is applied on the server, it pops-up a message like you faced: “This webpage is trying to communicate with your computer using a protocol that your security setting don’t allow”. You can simply allow the pop-up by clicking yes to be rendered option. No harm in that.

So in his case, it may be the browser is trying to access some url in the mhtml:http:// format and mhtml have been locked down on the remote server or in your IE settings, that could be a reason you are getting the pop-up alert.

Again, all the above observations are based on my google, might not be 100% correct, but one might have got the picture a bit. So nothing malicious in that request.

Comments

Popular posts from this blog

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T...

Breaking Excel password protection

If you came across an excel sheet asking for password for allowing to make any changes into it, you may want to unprotect it. All we need to do is to edit the xml file which comes intrinsically packaged with Excel 2007 or 2010. But what about Excel 2003? For that, open the Excel 2003 file within Excel 2007, save it as xlsx file. So, keep in mind all the Excel files below 2007 version, you need to convert them as Excel 2007 with extension .xlsx. Now here are the steps for doing that: 1. Open the Excel 2003 file (e.g. Secret.xlsx) and save it as .xlsx (Excel 2007) format. If you already have Excel 2007 file, then no need for any conversion. 2. Now change the extension of the above file to .zip and extract the zipped file. Browse through the file in the extracted folder and go to: <LocalPath>\Secret\xl\worksheets.   3. Now open the sheet/ sheets you want to remove protection in any xml editor. Look for keywords such as 'sheetProtection' or 'workbo...

jtool - an alternative to otool

jtool comes with a capability of running on Linux environment. Some ipa scanning tools are created to run on Linux environment where mac environment is not available. In such cases tools such as otool and class-dump-z will not work. So jtool can be an alternative to otool. For more information on jtool please refer to http://www.newosxbook.com/tools/jtool.html . It lists down various commands which have same output as otool or a equivalent. There are several commands mentioned in link. But for our customized requirements and basis checks I have listed down the below ones after running on many binaries. The outputs are similar or equivalent to otool and class-dump-z: Commands for checking PIE flag (ASLR) in jTool jtool -d -v -arch | grep stack ·           Automatic Reference Counting (ARC) protection: jtool -d -v -arch | grep _objc_release ·           To check if the devic...