CWE-800 소프트웨어 약점 상세 정보 | CVE Find

이름: Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors

CWE entries in this view (graph) are listed in the 2010 CWE/SANS Top 25 Programming Errors. This view is considered obsolete as a newer version of the Top 25 is available.

CWE 구성원

CWE-808: 2010 Top 25 - Weaknesses On the Cusp 카테고리

CWE-808: Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.

CWE-134: Use of Externally-Controlled Format String 기본

CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer 기본

CWE-307: Improper Restriction of Excessive Authentication Attempts 기본

CWE-330: Use of Insufficiently Random Values 기본

CWE-416: Use After Free 기본

CWE-426: Untrusted Search Path 기본

CWE-454: External Initialization of Trusted Variables or Data Stores 기본

CWE-456: Missing Initialization of a Variable 기본

CWE-476: NULL Pointer Dereference 기본

CWE-59: Improper Link Resolution Before File Access 기본

CWE-672: Operation on a Resource after Expiration or Release 기본

CWE-681: Incorrect Conversion between Numeric Types 기본

CWE-749: Exposed Dangerous Method or Function 기본

CWE-772: Missing Release of Resource after Effective Lifetime 기본

CWE-799: Improper Control of Interaction Frequency 기본

CWE-804: Guessable CAPTCHA 기본

CWE-803: 2010 Top 25 - Porous Defenses 카테고리

CWE-803: Weaknesses in this category are listed in the "Porous Defenses" section of the 2010 CWE/SANS Top 25 Programming Errors.

CWE-285: Improper Authorization 기본

CWE-306: Missing Authentication for Critical Functionality 기본

CWE-311: Missing Encryption of Sensitive Data 기본

CWE-327: Use of a Broken or Risky Cryptographic Algorithm 기본

CWE-732: Incorrect Permission Assignment for Critical Resource 기본

CWE-798: Use of Hard-coded Credentials 기본

CWE-807: Reliance on Untrusted Inputs in a Security Decision 기본

CWE-802: 2010 Top 25 - Risky Resource Management 카테고리

CWE-802: Weaknesses in this category are listed in the "Risky Resource Management" section of the 2010 CWE/SANS Top 25 Programming Errors.

CWE-120: Buffer Copy without Checking Size of Input 기본

CWE-129: Improper Validation of Array Index 기본

CWE-131: Incorrect Calculation of Buffer Size 기본

CWE-190: Integer Overflow or Wraparound 기본

CWE-22: Improper Limitation of a Pathname to a Restricted Directory 기본

CWE-494: Download of Code Without Integrity Check 기본

CWE-754: Improper Check for Unusual or Exceptional Conditions 기본

CWE-770: Allocation of Resources Without Limits or Throttling 기본

CWE-805: Buffer Access with Incorrect Length Value 기본

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program 기본

CWE-801: 2010 Top 25 - Insecure Interaction Between Components 카테고리

CWE-801: Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2010 CWE/SANS Top 25 Programming Errors.

CWE-209: Generation of Error Message Containing Sensitive Information 기본

CWE-352: Cross-Site Request Forgery 기본

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization 기본

CWE-434: Unrestricted Upload of File with Dangerous Type 기본

CWE-601: URL Redirection to Untrusted Site 기본

CWE-78: Improper Neutralization of Special Elements used in an OS Command 기본

CWE-79: Improper Neutralization of Input During Web Page Generation 기본

CWE-89: Improper Neutralization of Special Elements used in an SQL Command 기본

CWE 뷰 정보

취약점 매핑 메모

근거 : This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.
댓글 : Use this View or other Views to search and navigate for the appropriate weakness.

대상

이해관계자	설명
Software Developers	By following the Top 25, developers will be able to significantly reduce the number of weaknesses that occur in their software.
Product Customers	If a software developer claims to be following the Top 25, then customers can use the weaknesses in this view in order to formulate independent evidence of that claim.
Educators	Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could focus on the Top 25.

제출

이름	조직	날짜	출시일	Version
CWE Content Team	MITRE	2010-01-15 +00:00	2010-02-16 +00:00	1.8

수정 사항

이름	조직	날짜	댓글
CWE Content Team	MITRE	2017-11-08 +00:00	updated References
CWE Content Team	MITRE	2019-01-03 +00:00	updated Description
CWE Content Team	MITRE	2019-06-20 +00:00	updated References
CWE Content Team	MITRE	2020-02-24 +00:00	updated View_Audience
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2024-11-19 +00:00	updated References

참고 자료

REF-732

2010 CWE/SANS Top 25 Most Dangerous Software Errors
https://cwe.mitre.org/top25/archive/2010/2010_cwe_sans_top25.html