名稱: Use of Uninitialized Resource
The product uses or accesses a resource that has not been initialized.
一般資訊
引入方式
Implementation適用平台
程式語言
類別： Not Language-Specific (Undetermined)常見後果
| 範圍 | 影響 | 可能性 |
|---|---|---|
| Confidentiality | Read Memory, Read Application Data 注意：When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party. | |
| Availability | DoS: Crash, Exit, or Restart, DoS: Instability 注意：The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash. | |
| Other | Unexpected State, Varies by Context 注意：The consequences vary depending on the type of resource and how it is used within the product. |
觀察到的案例
| 參考資料 | 描述 |
|---|---|
CVE-2019-9805 | Chain: Creation of the packet client occurs before initialization is complete (CWE-696) resulting in a read from uninitialized memory (CWE-908), causing memory corruption. |
CVE-2008-4197 | Use of uninitialized memory may allow code execution. |
CVE-2008-2934 | Free of an uninitialized pointer leads to crash and possible code execution. |
CVE-2008-0063 | Product does not clear memory contents when generating an error message, leading to information leak. |
CVE-2008-0062 | Lack of initialization triggers NULL pointer dereference or double-free. |
CVE-2008-0081 | Uninitialized variable leads to code execution in popular desktop application. |
CVE-2008-3688 | Chain: Uninitialized variable leads to infinite loop. |
CVE-2008-3475 | Chain: Improper initialization leads to memory corruption. |
CVE-2005-1036 | Chain: Bypass of access restrictions due to improper authorization (CWE-862) of a user results from an improperly initialized (CWE-909) I/O permission bitmap |
CVE-2008-3597 | Chain: game server can access player data structures before initialization has happened leading to NULL dereference |
CVE-2009-2692 | Chain: Use of an unimplemented network socket operation pointing to an uninitialized handler function (CWE-456) causes a crash because of a null pointer dereference (CWE-476). |
CVE-2009-0949 | Chain: improper initialization of memory can lead to NULL dereference |
CVE-2009-3620 | Chain: some unprivileged ioctls do not verify that a structure has been initialized before invocation, leading to NULL dereference |
CVE-2008-5021 | Composite: race condition (CWE-362) allows attacker to modify an object while it is still being initialized, causing software to access uninitialized memory (CWE-908). |
潛在緩解措施
Phases : ImplementationExplicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Phases : Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Phases : Implementation
Avoid race conditions (CWE-362) during initialization routines.
Phases : Build and Compilation
Run or compile the product with settings that generate warnings about uninitialized variables or data.
偵測方法
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
漏洞對應備注
理由說明 : 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.
參考資料
REF-436
Exploiting Uninitialized Datamercy.
https://web.archive.org/web/20070403193636/http://www.felinemenace.org/~mercy/papers/UBehavior/UBehavior.zip
REF-1534
Automated Technical Debt Measure, Version 2OMG.
https://www.omg.org/spec/ATDM2/1.0/PDF
提交
| 名稱 | 機構 | 日期 | 發布日期 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 2.4 |
修改記錄
| 名稱 | 機構 | 日期 | 備註 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Observed_Examples | |
| CWE Content Team | MITRE | updated Description, Potential_Mitigations | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Detection_Factors, Observed_Examples | |
| CWE Content Team | MITRE | updated Common_Consequences, Demonstrative_Examples, Description, Observed_Examples, References |
