CWE-826 在预期生命周期中对资源的过早释放

Premature Release of Resource During Expected Lifetime

结构: Simple

Abstraction: Base

状态: Incomplete

被利用可能性: unkown

基本描述

The program releases a resource that is still intended to be used by the program itself or another actor.

扩展描述

This weakness focuses on errors in which the program should not release a resource, but performs the release anyway. This is different than a weakness in which the program releases a resource at the appropriate time, but it maintains a reference to the resource, which it later accesses. For this weaknesses, the resource should still be valid upon the subsequent access.

When a program releases a resource that is still being used, it is possible that operations will still be taken on this resource, which may have been repurposed in the meantime, leading to issues similar to CWE-825. Consequences may include denial of service, information exposure, or code execution.

相关缺陷

  • cwe_Nature: ChildOf cwe_CWE_ID: 666 cwe_View_ID: 1000 cwe_Ordinal: Primary

  • cwe_Nature: ChildOf cwe_CWE_ID: 666 cwe_View_ID: 699 cwe_Ordinal: Primary

  • cwe_Nature: CanPrecede cwe_CWE_ID: 672 cwe_View_ID: 1000

常见的影响

范围 影响 注释
Confidentiality ['Read Application Data', 'Read Memory'] If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.
Availability DoS: Crash, Exit, or Restart When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.
['Integrity', 'Confidentiality', 'Availability'] ['Execute Unauthorized Code or Commands', 'Modify Application Data', 'Modify Memory'] When the resource is released, the software might modify some of its structure. This might affect program logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.

分析过的案例

标识 说明 链接

Notes