Skip to main content

An Introduction to PDF XSS

Here I am going to give a brief write up about PDF XSS.

Amit Klien introduced a third kind of XSS attack-DOM Based XSS in which exploits client side vulnerabilities rather than Server Side flaws.He also observed how the # character can be used to, very conveniently, avoid sending attack payload to the server.DOM-based XSS typically uses JavaScript.Example (taken from Amit’s paper):

<HTML><TITLE>Welcome!</TITLE>Hi <SCRIPT>var pos = ocument.URL.indexOf("name=") + 5; document.write(document.URL.substring(pos,document.URL.length));</SCRIPT></HTML>

Exploiting PDF :Use the same technique using JavaScript it would execute it when a link in the following format is encountered:

After a successful attack the code is executed in the context of the site that hosts the PDF file.

The attacker is in full control of the victim’s browser (think session hijacking, request forgery, etc.).

Individual users are fully compromised.System compromise is possible through escalation.

Fixing the problem:
In many ways this is a simple problem to solve.

Just upgrade the client-side software:Adobe Reader 8 not vulnerable.Internet Explorer 7 not vulnerable.

Alternatively, you can configure the browser not to open PDF files at all.But we know many users will not upgrade.

Not possible to detect attack on the server.Therefore our only option is to “protect” all PDF files no matter if they are being attacked or not.Proposed mitigation revolves around three ideas:Moving PDF files to some other domain name.Preventing browsers from recognising PDF files. (Some are very stubborn in this regard.)Forcing browsers to download PDF files.


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. Th…

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…

Insecure protocols

Some basic insecure protocols and risk associated with them: