취약점 도입 방식
Architecture and Design : It is common practice for products to be designed to
use default keys. The rationale is to simplify the
manufacturing process or the system administrator's task of
installation and deployment into an enterprise. However,
there is a risk that admins might not change the defaults.
적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)
운영 체제
클래스: Not OS-Specific (Undetermined)
아키텍처
클래스: Not Architecture-Specific (Undetermined)
기술
클래스: Not Technology-Specific (Undetermined)
일반적인 결과
| 범위 |
영향 |
가능성 |
| Authentication | Gain Privileges or Assume Identity
참고: It is easier for attackers to bypass authentication quickly
across multiple organizations. | |
관찰된 예시
| 참고 자료 |
설명 |
| cloud cluster management product has a default master encryption key |
| backup storage product has a default SSH public key in the authorized_keys file, allowing root access |
| 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.
제출
| 이름 |
조직 |
날짜 |
출시일 |
Version |
| CWE Content Team |
MITRE |
2022-10-07 +00:00 |
2022-10-13 +00:00 |
4.9 |
수정 사항
| 이름 |
조직 |
날짜 |
댓글 |
| 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 |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Common_Consequences, Description, Modes_of_Introduction |