名稱: Improper Update of Reference Count
The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.
一般資訊
背景詳情
引入方式
Implementation適用平台
程式語言
名稱： C (Sometimes)名稱： C++ (Sometimes)
類別： Not Language-Specific (Undetermined)
常見後果
| 範圍 | 影響 | 可能性 |
|---|---|---|
| Availability | DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other) 注意：If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs. | High |
| Availability | DoS: Crash, Exit, or Restart 注意：If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation. | Low |
觀察到的案例
| 參考資料 | 描述 |
|---|---|
CVE-2002-0574 | Chain: reference count is not decremented, leading to memory leak in OS by sending ICMP packets. |
CVE-2004-0114 | Reference count for shared memory not decremented when a function fails, potentially allowing unprivileged users to read kernel memory. |
CVE-2006-3741 | Chain: improper reference count tracking leads to file descriptor consumption |
CVE-2007-1383 | Chain: integer overflow in reference counter causes the same variable to be destroyed twice. |
CVE-2007-1700 | Incorrect reference count calculation leads to improper object destruction and code execution. |
CVE-2008-2136 | Chain: incorrect update of reference count leads to memory leak. |
CVE-2008-2785 | chain/composite: use of incorrect data type for a reference counter allows an overflow of the counter, leading to a free of memory that is still in use. |
CVE-2008-5410 | Improper reference counting leads to failure of cryptographic operations. |
CVE-2009-1709 | Chain: improper reference counting in a garbage collection routine leads to use-after-free |
CVE-2009-3553 | Chain: reference count not correctly maintained when client disconnects during a large operation, leading to a use-after-free. |
CVE-2009-3624 | Reference count not always incremented, leading to crash or code execution. |
CVE-2010-0176 | improper reference counting leads to expired pointer dereference. |
CVE-2010-0623 | OS kernel increments reference count twice but only decrements once, leading to resource consumption and crash. |
CVE-2010-2549 | OS kernel driver allows code execution |
CVE-2010-4593 | improper reference counting leads to exhaustion of IP addresses |
CVE-2011-0695 | Race condition causes reference counter to be decremented prematurely, leading to the destruction of still-active object and an invalid pointer dereference. |
CVE-2012-4787 | improper reference counting leads to use-after-free |
漏洞對應備注
理由說明 : 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-884
Windows Kernel Reference Count Vulnerabilities - Case StudyMateusz "j00ru" Jurczyk.
https://j00ru.vexillium.org/slides/2012/zeronights.pdf
提交
| 名稱 | 機構 | 日期 | 發布日期 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 2.4 |
修改記錄
| 名稱 | 機構 | 日期 | 備註 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Type | |
| CWE Content Team | MITRE | updated Relationships, Type | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated References, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Background_Details, Common_Consequences, Description |
