Description
The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
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, if admins do not change the defaults, it is easier for attackers to bypass authentication quickly across multiple organizations.
Potential Impact
Authentication
Gain Privileges or Assume Identity
Demonstrative Examples
Mitigations & Prevention
Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
Force the administrator to change the credential upon installation.
The product administrator could change the defaults upon installation or during operation.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| 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 |
Related Weaknesses
Frequently Asked Questions
What is CWE-1392?
CWE-1392 (Use of Default Credentials) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
How can CWE-1392 be exploited?
Attackers can exploit CWE-1392 (Use of Default Credentials) to gain privileges or assume identity. This weakness is typically introduced during the Architecture and Design phase of software development.
How do I prevent CWE-1392?
Key mitigations include: Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
What is the severity of CWE-1392?
CWE-1392 is classified as a Base-level weakness (Medium abstraction). It has been observed in 5 real-world CVEs.