OWASP Top10 2017正式发布了 快来看新的10类应用安全风险
在5月份的时候，绿盟科技的Web应用安全专家解读了 owasp top10 2017 RC1，中 新增两类问题，“A7-攻击防护不足”以及“A10-未受有效保护的API”。今天 OWASP Top10 终于发布了2017正式版本，上一次版本是在2013年。在 owasp top10 2017 正式版中又有怎样的变化呢？
OWASP Top10是什么
OWASP Top 10不是一个官方文档或标准，而只是一个被广泛采用的意识文件，被用来分类网络安全漏洞的严重程度，目前被许多漏洞奖励平台和企业安全团队评估漏洞报告所采用。
OWASP Top 10多年来经历了几次迭代，之前的版本包括2004年、2007年、2010年、2013年和2017年发布。 与往年一样，注入仍然是应用安全风险的首要问题，但排名却出现了一些混乱，出现了三名新成员 ，他们是XML外部实体（XXE），不安全的反序列化，以及不足的记录和监控。 同前几年一样，排名是根据用户意见和公开讨论编写的。 下面是每个缺陷的描述列表，以及比较OWASP 2017 Top 10与旧版迭代的表格。
A1:2017-Injection
Injection flaws, such as SQL, NoSQL, 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:2017-Broken Authentication
Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently.
A3:2017-Sensitive Data Exposure
Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser.
A4:2017-XML External Entities (XXE)
Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks.
A5:2017-Broken Access Control
Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users' accounts, view sensitive files, modify other users’ data, change access rights, etc.
A6:2017-Security Misconfiguration
Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched and upgraded in a timely fashion.
A7:2017-Cross-Site Scripting (XSS)
XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. 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.
A8:2017-Insecure Deserialization
Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks.
A9:2017-Using Components with Known Vulnerabilities
Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts.
A10:2017-Insufficient Logging & Monitoring
Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.
| 2017 | 2013 | 2010 | 2007 | 2004 |
|---|---|---|---|---|
| Injection | Injection | Injection | Cross-Site Scripting (XSS) | Unvalidated Input |
| Broken Authentication | Broken Authentication and Session Management | Cross-Site Scripting (XSS) | Injection Flaws | Broken Access Control |
| Sensitive Data Exposure | Cross-Site Scripting (XSS) | Broken Authentication and Session Management | Malicious File Execution | Broken Authentication and Session Management |
| XML External Entities (XXE) | Insecure Direct Object References | Insecure Direct Object References | Insecure Direct Object Reference | Cross Site Scripting |
| Broken Access Control | Security Misconfiguration | Cross-Site Request Forgery (CSRF) | Cross-Site Request Forgery (CSRF) | Buffer Overflow |
| Security Misconfiguration | Sensitive Data Exposure | Security Misconfiguration | Information Leakage and Improper Error Handling | Injection Flaws |
| Cross-Site Scripting (XSS) | Missing Function Level Access Control | Insecure Cryptographic Storage | Broken Authentication and Session Management | Improper Error Handling |
| Insecure Deserialization | Cross-Site Request Forgery (CSRF) | Failure to Restrict URL Access | Insecure Cryptographic Storage | Insecure Storage |
| Using Components with Known Vulnerabilities | Using Components with Known Vulnerabilities | Insufficient Transport Layer Protection | Insecure Communications | Application Denial of Service |
| Insufficient Logging & Monitoring | Unvalidated Redirects and Forwards | Unvalidated Redirects and Forwards | Failure to Restrict URL Access | Insecure Configuration Management |
文章出处：本文由：bleepingcomputer 发布，版权归属于原作者。
官方
3.18K篇文章
194.39M总阅读量
