OWASP Top 10 Application Security Risks - 2010

2011. 4. 10. 08:45카테고리 없음




A1 – Injection (인젝션)
 
Injection flaws, such as SQL, OS, and LDAP injection, occur when untrusteddata 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. 

A2 – Cross-Site Scripting (XSS) (크로스 사이트 스크립팅)
 
XSS flaws occur whenever an application takes untrusteddata 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.

A3 – 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.

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 – 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.

A6 – 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.

A7 – 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.

A8 - Failure to Restrict URL Access (URL 접근 제한 실패)
 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.

A9 - 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.

A10 – Unvalidated Redirects and Forwards (검증되지 않은 리다이렉트와 포워드)
 Web applications frequently redirect and forward users to other pages and websites, and use untrusteddata to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages. 


* 자세한 내용은 첨부파일 참고


OWASP_T10_-_2010.pdf

OWASP_T10_-_2010_Korean.pdf