CWE-1393
Notifications for a CWE
Stay informed of any changes for a specific CWE.
Name: Use of Default Password
The product uses default passwords for potentially critical functionality.
CWE Description
It is common practice for products to be designed to use
default passwords 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,
then it makes it easier for attackers to quickly bypass
authentication across multiple organizations. There are many
lists of default passwords and default-password scanning tools
that are easily available from the World Wide Web.
General Informations
Modes Of Introduction
Architecture and DesignApplicable 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)Class: ICS/OT (Undetermined)
Common Consequences
| Scope | Impact | Likelihood |
|---|---|---|
| Authentication | Gain Privileges or Assume Identity |
Observed Examples
| References | Description |
|---|---|
CVE-2022-30270 | Remote Terminal Unit (RTU) uses default credentials for some SSH accounts |
CVE-2022-2336 | OPC Unified Architecture (OPC UA) industrial automation product has a default password |
CVE-2021-38759 | microcontroller board has default password |
CVE-2021-44480 | children's smart watch has default passwords allowing attackers to send SMS commands and listen to the device's surroundings |
CVE-2020-11624 | surveillance camera has default password for the admin account |
CVE-2018-15719 | medical dental records product installs a MySQL database with a blank default password |
CVE-2014-9736 | healthcare system for archiving patient images has default passwords for key management and storage databases |
CVE-2000-1209 | database product installs admin account with default null password, allowing privileges, as exploited by various worms |
Potential Mitigations
Phases : RequirementsProhibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
Phases : Documentation
Ensure that product documentation clearly emphasizes the presence of default passwords and provides steps for the administrator to change them.
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.
References
REF-1283
OT:ICEFALL: The legacy of "insecure by design" and its implications for certifications and risk managementForescout Vedere Labs.
https://www.forescout.com/resources/ot-icefall-report/
REF-1303
Researchers Out Default Passwords Packaged With ICS/SCADA WaresKelly Jackson Higgins.
https://www.darkreading.com/endpoint/researchers-out-default-passwords-packaged-with-ics-scada-wares
REF-1446
Secure by Design Alert: How Manufacturers Can Protect Customers by Eliminating Default PasswordsCybersecurity and Infrastructure Security Agency.
https://www.cisa.gov/resources-tools/resources/secure-design-alert-how-manufacturers-can-protect-customers-eliminating-default-passwords
Submission
| Name | Organization | Date | Date release | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 4.9 |
Modifications
| Name | Organization | Date | Comment |
|---|---|---|---|
| CWE Content Team | MITRE | updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes, Relationships | |
| CWE Content Team | MITRE | updated References |
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.