CWE-1393: Use of Default Password
The product uses default passwords for potentially critical functionality.
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.
Consequences
- Authentication: Gain Privileges or Assume Identity
How to prevent it
- Requirements: Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
- Documentation: Ensure that product documentation clearly emphasizes the presence of default passwords and provides steps for the administrator to change them.
- Architecture and Design: Force the administrator to change the credential upon installation.
- Installation, Operation: The product administrator could change the defaults upon installation or during operation.
Recent advisories
- GHSA-hj7x-hmf2-hc2p — Harbor allows the use of the default password for web UI login
- GHSA-gq3w-7jj3-x7gr — MLflow Use of Default Password Authentication Bypass Vulnerability
- GHSA-43xf-59vr-g4f2 — Liferay Portal Uses Default Password
- GHSA-57qh-vmjr-5jxg — Snipe-IT remote code execution
- CVE-2023-45249 — Remote command execution due to use of default passwords.
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor