이름: Use of Default Credentials

The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.

일반 정보

취약점 도입 방식

Array : It is common practice for products to be designed to use default keys, passwords, or other mechanisms for authentication. The rationale is to simplify the manufacturing process or the system administrator's task of installation and deployment into an enterprise. However, this places the responsibility of changing defaults onto the administrator.

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Undetermined)

운영 체제

클래스: Not OS-Specific (Undetermined)

아키텍처

클래스: Not Architecture-Specific (Undetermined)

기술

클래스: ICS/OT (Undetermined)
클래스: Not Technology-Specific (Undetermined)

일반적인 결과

범위	영향	가능성
Authentication	Gain Privileges or Assume Identity 참고: If admins do not change the defaults, it is easier for attackers to bypass authentication quickly across multiple organizations.

관찰된 예시

참고 자료	설명
CVE-2022-30270	Remote Terminal Unit (RTU) uses default credentials for some SSH accounts
CVE-2021-41192	data visualization/sharing package uses default secret keys or cookie values if they are not specified in environment variables
CVE-2021-38759	microcontroller board has default password, allowing admin access
CVE-2018-3825	cloud cluster management product has a default master encryption key
CVE-2010-2306	Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic

잠재적 완화 방법

Phases : Requirements
Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
Phases : Architecture and Design
Force the administrator to change the credential upon installation.
Phases : Installation // Operation
The product administrator could change the defaults upon installation or during operation.

취약점 매핑 메모

근거 : 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-1283

OT:ICEFALL: The legacy of "insecure by design" and its implications for certifications and risk management
Forescout Vedere Labs.
https://www.forescout.com/resources/ot-icefall-report/

제출

이름	조직	날짜	출시일	Version
CWE Content Team	MITRE	2022-10-07 +00:00	2022-10-13 +00:00	4.9

수정 사항

이름	조직	날짜	댓글
CWE Content Team	MITRE	2023-01-31 +00:00	updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References
CWE Content Team	MITRE	2023-04-27 +00:00	updated Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2024-11-19 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2025-12-11 +00:00	updated Observed_Examples, Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description, Modes_of_Introduction, Time_of_Introduction

CWE-1392 상세 정보

CWE-1392