Sposoby wprowadzenia
Architecture and Design : COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.
Odpowiednie platformy
Język
Class: Not Language-Specific (Undetermined)
Typowe konsekwencje
| Zakres |
Wpływ |
Prawdopodobieństwo |
| Access Control | Gain Privileges or Assume Identity | |
Potencjalne środki zaradcze
Passwords should be encrypted with keys that are at least 128 bits in length for adequate security.
Metody wykrywania
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Skuteczność : High
Uwagi dotyczące mapowania podatności
Uzasadnienie : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentarz : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Powiązane wzorce ataków
| CAPEC-ID |
Nazwa wzorca ataku |
| CAPEC-55 |
Rainbow Table Password Cracking
An attacker gets access to the database table where hashes of passwords are stored. They then use a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system. |
Notatki
Odniesienia
REF-6
Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors
Katrina Tsipenyuk, Brian Chess, Gary McGraw.
https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf REF-207
Building Secure Software: How to Avoid Security Problems the Right Way
John Viega, Gary McGraw.
REF-44
24 Deadly Sins of Software Security
Michael Howard, David LeBlanc, John Viega.
Zgłoszenie
| Nazwa |
Organizacja |
Data |
Data wydania |
Version |
| 7 Pernicious Kingdoms |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
Modyfikacje
| Nazwa |
Organizacja |
Data |
Komentarz |
|
Veracode |
2008-08-15 +00:00 |
Suggested OWASP Top Ten 2004 mapping |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Relationships, Other_Notes, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2009-07-27 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2011-03-29 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated References, Relationships |
| CWE Content Team |
MITRE |
2014-07-30 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2015-12-07 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Applicable_Platforms, Modes_of_Introduction, Relationships |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Description, Name, Other_Notes, References, Relationships, Type |
| CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Detection_Factors, Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Relationships, Weakness_Ordinalities |