Default or Well-Known Credentials

A system still accepts a vendor default or widely published username and password, so anyone who knows the product can sign in with it.

SeverityCritical
CVSS 3.19.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.09.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1392: Use of Default Credentials
OWASP Top 10A07:2025 Authentication Failures
MITRE ATT&CKT1078.001 Default Accounts
CategorySecurity Misconfiguration

Description

The application, device or service accepts a username and password that are set by the vendor at installation, printed in its documentation or otherwise widely known, such as admin with the password admin, a blank password or a product-specific default. Default credentials for most products are collected in public lists and built into attack tools, so they are among the first values any attacker tries. The attack needs no skill or prior access beyond network reachability, and is routinely automated by botnets and opportunistic attackers scanning the internet.

The weakness is most often found on administrative interfaces: application server managers, network, storage and virtualisation appliances, printers, CCTV and building management systems, database consoles, continuous integration and monitoring tools, and sample or setup accounts left behind by an installation. An attacker who can reach the login interface can sign in with the privileges of the default account, which on administrative interfaces usually means full control of the system. Depending on the product, this can allow the attacker to read and change its configuration and data, create further accounts, deploy code (for example a web application archive through an application server's manager), intercept or redirect traffic passing through a network device, or use the system as a foothold to attack the rest of the network.

The weakness is confirmed by signing in with the documented default for the identified product. Vulnerability scanners, Nmap scripts, Metasploit modules and dedicated default-credential checkers test common defaults automatically, and usually report the product, the account and the credential that worked. Related variants include a password set during a standard build and reused on every system of the same type, and passwords derived from the product, device or organisation name, which attackers try just as readily.

Remediation

  • Change the password of every default account to a unique, randomly generated value held in a password manager or privileged access management system, or disable or remove the account where the product allows it.
  • Make changing default credentials part of the build and commissioning process for every new system and device, and check it before the system goes live. Prefer products that require a unique password to be set at first use.
  • Remove sample applications, setup accounts and test users left behind by installation.
  • Restrict administrative interfaces to a management network or VPN, and require multi-factor authentication for them where the product supports it.
  • Test systems regularly for default credentials, for example with authenticated vulnerability scans, so that newly deployed or factory-reset devices are caught.

Where a device's credentials cannot be changed immediately, restrict access to its management interface to named administrative hosts as an interim measure. Confirm the fix by repeating the login attempts with the published defaults and confirming that each is rejected.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Authentication and Sessions Findings

Every Authentication and Sessions finding