CWE-788
Access of Memory Location After End of Buffer
2009-10-29
00h00 +00:00
00h00 +00:00
指定 CWE 通知
随时了解指定 CWE 的变更。
名称: Access of Memory Location After End of Buffer
The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.
基本信息
引入方式
Implementation : This typically occurs when a pointer or its index is incremented to a position after the buffer; or when pointer arithmetic results in a position after the buffer.适用平台
编程语言
类： Memory-Unsafe (Undetermined)名称： C (Often)
名称： C++ (Often)
常见后果
| 影响范围 | 影响 | 可能性 |
|---|---|---|
| Confidentiality | Read Memory 注意： For an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffer's position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences. | |
| Integrity Availability | Modify Memory, DoS: Crash, Exit, or Restart 注意： Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop. | |
| Integrity | Modify Memory, Execute Unauthorized Code or Commands 注意： If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can redirect a function pointer to their own malicious code. Even when the attacker can only modify a single byte arbitrary code execution can be possible. Sometimes this is because the same problem can be exploited repeatedly to the same effect. Other times it is because the attacker can overwrite security-critical application-specific data -- such as a flag indicating whether the user is an administrator. |
观察示例
| 参考资料 | 描述 |
|---|---|
CVE-2009-2550 | Classic stack-based buffer overflow in media player using a long entry in a playlist |
CVE-2009-2403 | Heap-based buffer overflow in media player using a long entry in a playlist |
CVE-2009-0689 | large precision value in a format string triggers overflow |
CVE-2009-0558 | attacker-controlled array index leads to code execution |
CVE-2008-4113 | OS kernel trusts userland-supplied length value, allowing reading of sensitive information |
CVE-2007-4268 | Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122) |
检测方法
Fuzzing
Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.有效性 : High
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.)有效性 : High
Automated Dynamic Analysis
Use tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518].有效性 : Moderate
漏洞映射说明
依据 : The CWE entry might be misused when lower-level CWE entries might be available. It also overlaps existing CWE entries and might be deprecated in the future.备注 : If the "Access" operation is known to be a read or a write, then investigate children of entries such as CWE-787: Out-of-bounds Write and CWE-125: Out-of-bounds Read.
参考资料
REF-961
Automated Source Code Reliability Measure (ASCRM)Object Management Group (OMG).
http://www.omg.org/spec/ASCRM/1.0/
REF-1518
AddressSanitizerhttps://clang.llvm.org/docs/AddressSanitizer.html
REF-1534
Automated Technical Debt Measure, Version 2OMG.
https://www.omg.org/spec/ATDM2/1.0/PDF
提交记录
| 名称 | 组织 | 日期 | 发布日期 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.6 |
修改记录
| 名称 | 组织 | 日期 | 备注 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Common_Consequences, Demonstrative_Examples, Observed_Examples | |
| CWE Content Team | MITRE | updated References, Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Detection_Factors, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Applicable_Platforms | |
| CWE Content Team | MITRE | updated Affected_Resources, Demonstrative_Examples, Functional_Areas | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Detection_Factors, References, Time_of_Introduction, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Description, Dimensions, Modes_of_Introduction, References, Relationships |
