Skip to main content

Reflected XSS on SearchSecurity.com


SearchSecurity.com- A prominent online Information Security website which is resource for IT Security professionals for latest security news,attacks,security topics,whitepapers etc is itself vulnerable to reflected XSS.
The XSS is possible in response page which gives error message if the login fails.

An error page, which is handling requests for a non existing pages, a classic 404 error page.



If we request some non-existent the application returns following response:

Requesting http://example.com/non-existent_page.htm will return

Sorry non_existent_page not available

Here the application is embedding the requested page's name in the response.So if a user requests http://example.com/<script>alert("XSS in reponse page");</script> the application will execute the script when returning a response to the user.

Similarly the Login page of the SearchSecurity.com returns error message in response page.

....html?Error=Password+provided+is+incorrect.

So replacing it with

....html?Error=<script>alert("XSS");</script> will execute in the browser.

Also the application provides login-specific errors.
If username doesn't match :Email provided does not exist
If Password doesn't match :Password provided is incorrect

So Guessing usernames and passwords should not be very difficult for a determined attacker.

Comments

Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

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

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 device is jailbroken: jtool -d -v -arch | grep jail ·           Dyldinfo compatible options