| 6.5.1 | Injection
| Injection flaws, such as SQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing unauthorized data.
| 6.5.2 | A2 - Injection Flaws |
| 6.5.2 | Cross-Site Scripting (XSS)
| XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation and escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
| 6.5.1 | A1 –CrossSite Scripting (XSS) |
| 6.5.3 | Broken Authentication and Session Management
| Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, session tokens, or exploit other implementation flaws to assume other users’ identities.
| 6.5.7 | A7 –Broken Authentication and Session Management |
| 6.5.4 | Insecure Direct Object References
| A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.
| 6.5.4 | A4 –Insecure Direct Object Reference |
| 6.5.5 | Cross-Site Request Forgery (CSRF)
| A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
| 6.5.5 | A5 –Cross Site Request Forgery (CSRF) |
| 6.6.6 | Security Misconfiguration
| Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. All these settings should be defined, implemented, and maintained as many are not shipped with secure defaults. This includes keeping all software up to date, including all code libraries used by the application.
| Not Present | Not Present |
| 6.6.7 | Insecure Cryptographic Storage
| Many web applications do not properly protect sensitive data, such as credit cards, SSNs, and authentication credentials, with appropriate encryption or hashing. Attackers may steal or modify such weakly protected data to conduct identity theft, credit card fraud, or other crimes.
| 6.5.8 | A8 –Insecure Cryptographic Storage |
| 6.6.8 | Failure to Restrict URL Access
| Many web applications check URL access rights before rendering protected links and buttons. However, applications need to perform similar access control checks each time these pages are accessed, or attackers will be able to forge URLs to access these hidden pages anyway.
| 6.5.10 | A10 –Failure to Restrict URL Access |
| 6.6.9 | Insufficient Transport Layer Protection
| Applications frequently fail to authenticate, encrypt, and protect the confidentiality and integrity of sensitive network traffic. When they do, they sometimes support weak algorithms, use expired or invalid certificates, or do not use them correctly.
| 6.5.9 | A9 –InsecureCommunications |
| 6.6.10 | Unvalidated Redirects and Forwards
| Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.
| Not Present | Not Present |
