|
A1-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 data without proper authorization.
|
|
A2-Broken Authentication and Session Management
|
Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys,
or session tokens, or to exploit other implementation flaws to assume other users’ identities.
|
|
A3-Cross-Site Scripting (XSS)
|
XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or 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.
|
|
A4-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.
|
|
A5-Security Misconfiguration
|
Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and
platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.
|
|
A6-Sensitive Data Exposure
|
Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such
weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
|
|
A7-Missing Function Level Access Control
|
Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access
control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.
|
|
A8-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.
|
|
A9-Using Components with Known Vulnerabilities
|
Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If a vulnerable component is exploited, such an
attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts.
|
|
A10-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.
|
A1–注入
注入攻击漏洞。比如SQL，OS以及 LDAP注入。这些攻击发生在当不可信的数据作为命令或
者查询语句的一部分，被发送给解释器的时候。攻击者发送的恶意数据能够欺骗解释器，
A2–失效的身份认证和会话管理
与身份认证和会话管理相关的应用程序功能往往得不到正确的实现。这就导致了攻击者破
坏password、密匙、会话令牌或攻击其它的漏洞去冒充其它用户的身份。
A3–跨站脚本（XSS）
当应用程序收到含有不可信的数据，在没有进行适当的验证和转义的情况下。就将它发送
给一个网页浏览器，这就会产生跨站脚本攻击（简称XSS）。XSS同意攻击者在受害者的浏览
器上运行脚本，从而劫持用户会话、危害站点、或者将用户转向至恶意站点。
A4–
不安全的直接对象引用
•当开发者暴露一个对内部实现对象的引用时。比如。一个文件、文件夹或者数据库密匙，
就会产生一个不安全的直接对象引用。在没有訪问控制检測或其它保护时，攻击者会操控
这些引用去訪问未授权数据。
A5–
安全配置错误
好的安全须要相应用程序、框架、应用程序server、webserver、数据库server和平台定义
和运行安全配置。因为很多设置的默认值并非安全的，因此，必须定义、实施和维护这
些设置。这包括了对全部的软件保持及时地更新，包括全部应用程序的库文件。
A6–
敏感信息泄漏
很多Web应用程序没有正确保护敏感数据，如信用卡，税务ID和身份验证凭据。攻击者可能
会窃取或篡改这些弱保护的数据以进行信用卡诈骗、身份窃取，或其它犯罪。敏感数据值
需额外的保护。比方在存放或在传输过程中的加密。以及在与浏览器交换时进行特殊的预
防措施。
A7–
功能级訪问控制缺失
•大多数Web应用程序在功能在UI中可见曾经，验证功能级别的訪问权限。可是。应用程序需
要在每一个功能被訪问时在server端运行同样的訪问控制检查。假设请求没有被验证，攻击
者可以伪造请求以在未经适当授权时訪问功能。
A8–
跨站请求伪造 （CSRF）
一个跨站请求伪造攻击迫使登录用户的浏览器将伪造的HTTP请求，包含该用户的会话cookie
和其它认证信息。发送到一个存在漏洞的web应用程序。这就同意了攻击者迫使用户浏览器
向存在漏洞的应用程序发送请求，而这些请求会被应用程序觉得是用户的合法请求。
A9–
使用含有已知漏洞的组件
组件，比方：库文件、框架和其他软件模块，差点儿总是以所有的权限执行。假设一个带有
漏洞的组件被利用。这样的攻击能够造成更为严重的数据丢失或server接管。应用程序使用
带有已知漏洞的组件会破坏应用程序防御系统。并使一系列可能的攻击和影响成为可能。
A10–
未验证的重定向和转发
Web应用程序常常将用户重定向和转发到其它网页和站点，而且利用不可信的数据去判定
目的页面。假设没有得到适当验证，攻击者能够重定向受害用户到钓鱼软件或恶意站点。
或者使用转发去訪问未授权的页面。