名稱: Expired Pointer Dereference
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
一般資訊
背景詳情
引入方式
Implementation適用平台
程式語言
類別： Memory-Unsafe (Undetermined)名稱： C (Undetermined)
名稱： C++ (Undetermined)
常見後果
| 範圍 | 影響 | 可能性 |
|---|---|---|
| Confidentiality | Read Memory 注意：If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application. | |
| Availability | DoS: Crash, Exit, or Restart 注意：If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur. | |
| Integrity Confidentiality Availability | Execute Unauthorized Code or Commands 注意：If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible. |
觀察到的案例
| 參考資料 | 描述 |
|---|---|
CVE-2023-26463 | Chain: IPSec VPN product uses the same variable for multiple purposes in the same function (CWE-1109), leading to incorrect access control (CWE-284) and expired pointer dereference (CWE-825) |
CVE-2008-5013 | access of expired memory address leads to arbitrary code execution |
CVE-2010-3257 | stale pointer issue leads to denial of service and possibly other consequences |
CVE-2008-0062 | Chain: a message having an unknown message type may cause a reference to uninitialized memory resulting in a null pointer dereference (CWE-476) or dangling pointer (CWE-825), possibly crashing the system or causing heap corruption. |
CVE-2007-1211 | read of value at an offset into a structure after the offset is no longer valid |
潛在緩解措施
Phases : Architecture and DesignChoose a language that provides automatic memory management.
Phases : Implementation
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
偵測方法
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.)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
漏洞對應備注
理由說明 : 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.備註 : 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.
備注
There are close relationships between incorrect pointer dereferences and other weaknesses related to buffer operations. There may not be sufficient community agreement regarding these relationships. Further study is needed to determine when these relationships are chains, composites, perspective/layering, or other types of relationships. As of September 2010, most of the relationships are being captured as chains.Many weaknesses related to pointer dereferences fall under the general term of "memory corruption" or "memory safety." As of September 2010, there is no commonly-used terminology that covers the lower-level variants.
參考資料
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.10 |
修改記錄
| 名稱 | 機構 | 日期 | 備註 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Demonstrative_Examples, Potential_Mitigations, Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Relationships | |
| CWE Content Team | MITRE | updated Alternate_Terms | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Research_Gaps | |
| CWE Content Team | MITRE | updated Common_Consequences, Description | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Applicable_Platforms | |
| CWE Content Team | MITRE | updated Affected_Resources, Functional_Areas | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Detection_Factors, Observed_Examples, References, Time_of_Introduction, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Background_Details, Description, References |
