CWE-1392: Use of Default Credentials

Base

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.

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.
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-5fpv-5qvh-7cf3 — NodeJS version of the HAX CMS application is distributed with Default Secrets
GHSA-cm2r-rg7r-p7gg — File Browser vulnerable to insecure password handling

All advisories for CWE-1392

Is this in your code?

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