CWE-1394 — Use of Default Cryptographic Key
CWE-1394: Use of Default Cryptographic Key
MITRE CWE weakness
| Kind | Weakness |
| Abstraction | Base |
| Status | Incomplete |
| Likelihood of exploit | — |
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
- Authentication: Gain Privileges or Assume Identity
Mitigations
Requirements — Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
Architecture and Design — Force the administrator to change the credential upon installation.
Installation — The product administrator could change the defaults upon installation or during operation.
References
- CWE page: https://cwe.mitre.org/data/definitions/1394.html
- CWE list: https://cwe.mitre.org/data/index.html