Skip to main content

'Information Leakage-Improper Error Handling' dropped

From Owasp Top 10 2010 List, the issue 'Information Leakage-Improper Error Handling' has been dropped. But it's not the final list,its child release actually. Bu I feel it shouldn't be set aside because its still the one of the prevalent issues these days. That's why I mailed to Dave Wicher:
Hi Dave,

Excellent work, Congrats!

Just one little query- Don't you think that Information Leakage & Improper
Error Handling still deserves to be in Top 10?
Dave replied:

This topic is clearly a very prevalent issue that deserves attention by
most organizations. However, the typical impact of such a flaw is usually very low. Therefore, the overall risk of this type of flaw is lower than the other items in the top 10, which is why it was replaced in this update with one of the 2 new items.
Regarding dropping Info Leak/Error handling - It is incredibly

prevalent, no question. But their impact is typically very low, so the

overall risk is low, which is why it fell out of this new risk focused

top 10. It doesn't mean this isn't important, but the other items in our

opinion introduce more risk.
We'd rather have people spend more time fixing the actual flaws than

focusing on fixing info leak/error handling that help them find actual

flaws.

Dave


Comments

NaPsTeR said…
Hi Nilesh

I just stumbled onto your blog and have found it very interesting. Congrats and keep up the good work !

I agree with your comment and your concern about Information Leakage. Actually in the Information Security world, that is a severe problem called as DATA BREACH. There is a lot of topics that include Data breaches, the precautions and forensics related to that. There has been already a lot of research being done to have a clause in the policy for its disclosure and the related options for prevention. So, during my lectures too I retorted several times to the professors that once there is a data breach, all the information related to that guy is gone i.e. the guy is in big trouble. He can be harmed not only now, later and I don't know there are many ways to extort money and likes. Again, I am one of the kinds who thinks that Data breaches are severely underrated. I would love to get some more info about this from you and other researchers you know.

Thanks

Nipun
vitamine b12 said…
You may think that your policies, procedures, tools, techniques and appliances are enough to secure and protect your data. You would probably be dumbfounded to find out just how much data- confidential, private, sensitive data that nobody has any business seeing- is available via the Web if you just know the right search term syntax to use. To learn more about the problem of information leakage, how to determine if your data is at risk, and steps to take to secure your data and remove it from Web search engines, read Information Leakage: Protect Against 'Google Hacking'.
Nilesh Kumar said…
@ Napster

Hi Nipun, Thanks a lot for commenting and surely I will let you know any info I ahve on Data Breaches. You can contact me at: nileshkumar83@gmail.com

Thanks,
Nilesh

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

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be

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