Skip to main content

SMTP Injection-Part I

Yet another injection attack! Same cause- Failure to validate user input. The application which I was assessing was almost injection free- means all the known issues like SQL Injection, XSS etc were not present until I found SMTP injection!

The application had one feedback/suggestion form, through which user can submit their comments. Typically, user-supplied input will be inserted into the SMTP conversation that the application server conducts with the mail server.
The form was having the following fields:
Your email address: Where user has to enter his email id
Subject: Enter the subject
Comments: User can put his comments
Entering the above information the user can submit the form by clicking on a nice Submit button. The mail will be fired to Admin of the website and few other stakeholders too.

So, for example if we specify the following:
Your email address: nileshkumar83@gmail.com
Subject: Flaws in the website
Comments: Your website has the lots of flaws that can be exploited..blah..blah.

Ideally clicking on Submit button should fire the email to Admin and few stakeholders not to anybody else!

Now suppose I inject the following in the Your email address field:
nileshkumar83@gmail.com%0aBcc:allotherpeople@thecompany.com

So this causes the mail command to generate the following headers:

To: admin@thecompany.com;stakeholder@thecompany.com
From: nileshkumar83@gmail.com
Bcc: allotherpeople@thecompany.com
Subject: Flaws in the website
Your website has the lots of flaws that can be exploited..blah..blah.

The %0a translated into new line and then follows Bcc command which send the mail to other people silently who are not directly concerned with the message.
So it may be used to create spam messages or malign anybody's image.
Another variant of the SMTP Injection is SMTP command injection in which can cause to create an entirely new message in which you can control the From headers as well. That is more dangerous. We'll talk about that in next part.

Comments

Post a Comment

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...
5 comments
Read more

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...
4 comments
Read more

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.
Post a Comment
Read more