Introductiemodi
Implementation
Toepasselijke platforms
Taal
Class: Not Language-Specific (Often)
Veelvoorkomende gevolgen
| Bereik |
Impact |
Waarschijnlijkheid |
| Other | Varies by Context | |
Waargenomen voorbeelden
| Referenties |
Beschrijving |
| large ID in packet used as array index |
| negative array index as argument to POP LIST command |
Mogelijke risicobeperkingen
Phases : Implementation
Detectiemethoden
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.)
Effectiviteit : High
Notities kwetsbaarheidsmapping
Rechtvaardiging : 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.
Opmerking : 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.
Notities
This entry is still under development and will continue to see updates and content improvements.
Indiening
| Naam |
Organisatie |
Datum |
Releasedatum |
Version |
| CWE Content Team |
MITRE |
2020-06-24 +00:00 |
2020-02-24 +00:00 |
4.1 |
Wijzigingen
| Naam |
Organisatie |
Datum |
Opmerking |
| CWE Content Team |
MITRE |
2021-03-15 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Detection_Factors, Weakness_Ordinalities |