Skip to main content

Memory leakage in 2-tier applications

The 2-tier applications use front-end to directly communicate to DB. There's no separate business logic tier. All the business logic are at client side. Thick client applications (mostly) are classic examples of that. Applications developed in .Net and Java could be found in big nos. inside any organization. Sometimes it's difficult to straightaway move to 3-tier architecture. Businesses are reluctant to accept this approach due to:
- Moving towards 3-tier involves a great amount of coding efforts and  money.
- Sometimes the applications are almost end of life and are not being retired just because of there;s no good reason to do so. 
- Most of the above applications are Intranet applications. Business claims that being an internal application, this is less susceptible to attack.

But they forget one very big risk under these claims- sensitive information in memory dumps. 

The application being 2-tier connects to DB while constructing the connection string using DB credentials, server name, DB name, port no. etc. These are at risk of being exposed when the client wants to connect to DB. 

But how an attacker can get the dump? He needs to have physical access to the victim's machine. So it's impossible. But we are not talking about an external attacker, we are talking about if the valid user of the application himself turns malicious. He can take the memory dump and find grab the sensitive information such as DB connection string. The soul of an application, ie, DB is compromised, bypassing the business layer. The business doesn't understand this.

So, any fix? There's no fix! As long as the app is 2-tier, there's no fix. However there are compensating controls- make it hard to grab the info from memory. 
- SecureString class- https://msdn.microsoft.com/en-/library/system.security.securestring(v=vs.110).aspx 
But only supported for .Net 4.5 and above. Represents text that should be kept confidential, such as by deleting it from computer memory when no longer needed. This class cannot be inherited.

- Write own code to overwrite the memory location- garbage collection. I saw a code by one developer which does it, to avoid password being exposed in memory. But you have to construct the connectionstring at some point of time, even momentarily, so that the app will connect to the DB and then quickly overwrite that. This reduces the attack window by a large extent- but not fixes it.

There's no real fix than moving to 3-tier architecture.For  2-tier we have to accept the risk.

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