CWE-1295
Debug Messages Revealing Unnecessary Information
2020-08-20
00h00 +00:00
00h00 +00:00
특정 CWE 알림
특정 CWE의 변경 사항에 대한 정보를 받아보세요.
이름: Debug Messages Revealing Unnecessary Information
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
일반 정보
취약점 도입 방식
Implementation적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)운영 체제
클래스: Not OS-Specific (Undetermined)아키텍처
클래스: Not Architecture-Specific (Undetermined)기술
클래스: Not Technology-Specific (Undetermined)일반적인 결과
| 범위 | 영향 | 가능성 |
|---|---|---|
| Confidentiality Integrity Availability Access Control Accountability Authentication Authorization Non-Repudiation | Read Memory, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Varies by Context | Medium |
관찰된 예시
| 참고 자료 | 설명 |
|---|---|
CVE-2022-34364 | Java-based SDK for TLS has a debug message with unnecessary information |
CVE-2021-25476 | Digital Rights Management (DRM) capability for mobile platform leaks pointer information, simplifying ASLR bypass |
CVE-2020-24491 | Processor generates debug message that contains sensitive information ("addresses of memory transactions"). |
CVE-2017-18326 | modem debug messages include cryptographic keys |
잠재적 완화 방법
Phases : ImplementationEnsure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
탐지 방법
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.)취약점 매핑 메모
근거 : 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.
관련 공격 패턴
| CAPEC ID | 공격 패턴 이름 |
|---|---|
| CAPEC-121 | Exploit Non-Production Interfaces
|
참고 자료
REF-1112
Android Security Bulletin - December 2018https://source.android.com/docs/security/bulletin/2018-12-01
제출
| 이름 | 조직 | 날짜 | 출시일 | Version |
|---|---|---|---|---|
| Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi | Intel Corporation | 4.2 |
수정 사항
| 이름 | 조직 | 날짜 | 댓글 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Observed_Examples, Related_Attack_Patterns, Relationships | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Observed_Examples, References, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Detection_Factors, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Relationships |
