Modes Of Introduction
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.
Applicable Platforms
Language
Class: Not Language-Specific (Undetermined)
Operating Systems
Class: Not OS-Specific (Undetermined)
Architectures
Class: Not Architecture-Specific (Undetermined)
Technologies
Class: Not Technology-Specific (Undetermined)
Common Consequences
| Scope |
Impact |
Likelihood |
| Authentication | Gain Privileges or Assume Identity
Note: It is easier for attackers to bypass authentication quickly
across multiple organizations. | |
Observed Examples
| References |
Description |
| 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 |
Potential Mitigations
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.
Vulnerability Mapping Notes
Justification : 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.
Comment : 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.
Submission
| Name |
Organization |
Date |
Date release |
Version |
| CWE Content Team |
MITRE |
2022-10-07 +00:00 |
2022-10-13 +00:00 |
4.9 |
Modifications
| Name |
Organization |
Date |
Comment |
| 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 |