CWE-788: Access of Memory Location After End of Buffer
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.
扩展描述
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.
常见后果
影响范围: 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.
检测方法
方法: 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
观察示例
参考: 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)
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| OMG ASCRM | ASCRM-CWE-788 | - |