Chi tiết CWE-14

Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal."

Các cách xuất hiện

Array
Build and Compilation

Nền tảng áp dụng

Ngôn ngữ

Tên: C (Undetermined)
Tên: C++ (Undetermined)
Lớp: Compiled (Undetermined)

Kiến trúc

Lớp: Not Architecture-Specific (Undetermined)

Hậu quả phổ biến

Các biện pháp giảm thiểu tiềm năng

Phases : Implementation
Store the sensitive data in a "volatile" memory location if available.
Phases : Build and Compilation
If possible, configure the compiler so that it does not remove dead stores.
Phases : Architecture and Design
Where possible, encrypt sensitive data that are used by a software system.

Phương pháp phát hiện

Black Box

This specific weakness is impossible to detect using black box methods. While an analyst could examine memory to see that it has not been scrubbed, an analysis of the executable would not be successful. This is because the compiler has already removed the relevant code. Only the source code shows whether the programmer intended to clear the memory or not, so this weakness is indistinguishable from others.
Hiệu quả : Limited

White Box

This weakness is only detectable using white box methods (see black box detection factor). Careful analysis is required to determine if the code is likely to be removed by the compiler.

Ghi chú ánh xạ lỗ hổng

Lý do : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Bình luận : 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.

Tài liệu tham khảo

REF-6

Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors
Katrina Tsipenyuk, Brian Chess, Gary McGraw.
https://cwe.mitre.org/documents/sources/SevenPerniciousKingdoms.pdf

REF-7

Writing Secure Code
Michael Howard, David LeBlanc.
https://www.microsoftpressstore.com/store/writing-secure-code-9780735617223

REF-124

When scrubbing secrets in memory doesn't work
Michael Howard.
https://seclists.org/bugtraq/2002/Nov/48

REF-125

Some Bad News and Some Good News
Michael Howard.
https://learn.microsoft.com/en-us/previous-versions/ms972826(v=msdn.10)

REF-126

GNU GCC: Optimizer Removes Code Necessary for Security
Joseph Wagner.
https://seclists.org/bugtraq/2002/Nov/266

Gửi

Sửa đổi