Vulnerabilities in Web Applications

Vulnerabilities in web application

A vulnerability is a system flaw or weakness in an application that could be exploited to compromise the security of the application. These crimes target the confidentiality, integrity, or availability (known as the “CIA triad”) of resources possessed by an application, its creators, and its users.
It’s not until after a breach has occurred that web security becomes a priority. 

They could be categorized as:

• Anti CSRF Tokens Scanner
• Insecure Component
• SQL Injection
• Source Code Disclosure
• Directory Browsing
• Insecure HTTP Method - Trace
• User Controllable Javascript Event (XSS)
• X-Frame-Options Header not set
• Big Redirects
• Content Security Policy Header not set
• Server leaks information by "X-Powered-By" in HTTP response
• Server leaks information by "Server" in HTTP response
• Web Browser XSS Protection Not Enabled
• X-Content-Type-Options Header Missing
• Sensitive Data Exposure - Base64 Disclosure
• Non-Storable Content
• Timestamp Disclosure Unix
• Broken Authentication

Why to check for  vulnerability or doing penetration testing?
 
As, hacking of website is getting increase day by day, here comes the role of web application security scanners. Web Application Security Scanner is a software program which performs automatic black box testing on a web application and identifies security vulnerabilities. Scanners do not access the source code, they only perform functional testing and try to find security vulnerabilities.


Tools to check vulnerability or to  penetration testing:

• ZAP [Preferred as used]
• SQLMap [Preferred as used]
• Grabber
• Vega
• Zed Attack Proxy
• Wapiti
• WebScarab
• Skipfish
• Ratproxy
• Wfuzz
• Watcher
• X5S
• Arachni         

See, ZAP and SQLMap both are open source and I had used it for checking vulnerabilities, both tool have power to build maximum scenarios.