Use of Default Cryptographic Key
Incomplete Base
Structure: Simple
Description
The product uses a default cryptographic key for potentially critical functionality.
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, if admins do not change the defaults, it is easier for attackers to bypass authentication quickly across multiple organizations.
Common Consequences 1
Scope: Authentication
Impact: Gain Privileges or Assume Identity
Potential Mitigations 3
Phase: Requirements
Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
Effectiveness: High
Phase: Architecture and Design
Force the administrator to change the credential upon installation.
Effectiveness: High
Phase: InstallationOperation
The product administrator could change the defaults upon installation or during operation.
Effectiveness: Moderate
Observed Examples 3
CVE-2018-3825cloud cluster management product has a default master encryption key
CVE-2016-1561backup storage product has a default SSH public key in the authorized_keys file, allowing root access
CVE-2010-2306Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Technologies:
Not Technology-Specific : Undetermined
Modes of Introduction
Architecture and Design
Related Weaknesses