Các cách xuất hiện
Implementation
Nền tảng áp dụng
Ngôn ngữ
Lớp: Not Language-Specific (Undetermined)
Hệ điều hành
Lớp: Not OS-Specific (Undetermined)
Kiến trúc
Lớp: Not Architecture-Specific (Undetermined)
Công nghệ
Lớp: Not Technology-Specific (Undetermined)
Hậu quả phổ biến
| Phạm vi |
Tác động |
Khả năng xảy ra |
Confidentiality Integrity Availability Access Control Accountability Authentication Authorization Non-Repudiation | Read Memory, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Varies by Context | Medium |
Ví dụ đã quan sát
| Tài liệu tham khảo |
Mô tả |
| Java-based SDK for TLS has a debug message with unnecessary information |
| Digital Rights Management (DRM) capability for mobile platform leaks pointer information, simplifying ASLR bypass |
| Processor generates debug message that contains sensitive information ("addresses of memory transactions"). |
| modem debug messages include cryptographic keys |
Các biện pháp giảm thiểu tiềm năng
Phases : Implementation
Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
Phương pháp phát hiện
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.)
Ghi chú ánh xạ lỗ hổng
Lý do : 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.
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.
Mẫu tấn công liên quan
| ID CAPEC |
Tên mẫu tấn công |
| CAPEC-121 |
Exploit Non-Production Interfaces
|
Tài liệu tham khảo
REF-1112
Android Security Bulletin - December 2018
https://source.android.com/docs/security/bulletin/2018-12-01
Gửi
| Tên |
Tổ chức |
Ngày |
Ngày phát hành |
Version |
| Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi |
Intel Corporation |
2020-05-31 +00:00 |
2020-08-20 +00:00 |
4.2 |
Sửa đổi
| Tên |
Tổ chức |
Ngày |
Bình luận |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Observed_Examples, Related_Attack_Patterns, Relationships |
| CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated References |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Observed_Examples, References, Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2023-10-26 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2025-09-09 +00:00 |
updated References |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Detection_Factors, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-04-30 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Relationships |