Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

Why Are Default Passwords a Security Risk?

Default passwords are the factory credentials shipped with a device or application. Because they are identical across every unit and published online, they turn one weak secret into a fleet-wide compromise.

Illustration for the cybersecurity term Default Passwords
Home / Blog / Cybersecurity Terms / Why Are Default Passwords a Security Risk?
17 November 2026

Why Are Default Passwords a Security Risk?

Why Are Default Passwords a Security Risk?

A default password is the credential a device, appliance, or application ships with before anyone configures it. The problem is not that the password is short; it is that it is the same on every unit sold, printed in a manual that is available as a PDF, and collected in searchable lists that anyone can download. The secret stopped being a secret at the factory.

Three variants matter, and they are not equally fixable:

How They Are Found

At scale, through search. Shodan and Censys index banners from internet-facing services, so an attacker filters for a specific camera model or router firmware and receives a list of live targets. Credential lists such as the long-running default password catalogues then supply the login pairs. The whole sequence is scripted and takes minutes, which is why exposure time for a newly connected device is measured in hours.

Internally the route is different but no easier to defend. Printers, building controllers, KVM switches, out-of-band management cards, and test databases retain their factory logins because nobody owns them. Once an attacker has a foothold, those boxes supply credentials, network access, and a quiet place to persist, which is how lateral movement usually begins.

What It Has Cost

Mirai remains the canonical case. The malware carried just 61 username and password pairs — root/xc3511, root/vizxv, admin/admin1234 and similar — and tried them over Telnet against anything that answered. That was enough to assemble a botnet of hundreds of thousands of cameras and routers, generate a roughly 620 Gbps flood against the KrebsOnSecurity site in September 2016, and knock the DNS provider Dyn offline on 21 October 2016. The source code was published on 30 September 2016 and its descendants are still active.

Hardcoded accounts keep appearing in professional equipment too. In December 2020, researchers at Eye Control disclosed an undocumented administrative account in several Zyxel firewalls and VPN gateways, tracked as CVE-2020-29583; the credentials sat in the firmware and no amount of configuration would remove them. Exploitation against exposed devices started within days of disclosure.

Fixing It as an Operator

  1. Inventory first. Build a list of every device with a management interface, including the ones procurement bought without telling anyone.
  2. Change credentials during commissioning, as a documented build step rather than a hope, and record completion.
  3. Scan for defaults deliberately. Nmap scripts, Nessus default credential checks, and simple internal sweeps find them quickly; so will an attacker.
  4. Remove management interfaces from the internet entirely and place them behind a VPN or jump host.
  5. Use multi-factor authentication and central identity where the device supports it, so there is no local password to forget about.
  6. Ask suppliers, in writing, whether the product contains any account not visible to the administrator.

Fixing It as a Manufacturer

The design answer is a unique per-device secret generated at production, printed on a label or in the packaging, and accompanied by a forced change on first use. Better still, bind the first setup to physical possession — a QR code, a button press, or a pairing flow — so network reachability alone is never enough.

In the UK this is now a legal duty rather than good practice. Since 29 April 2024 the Product Security and Telecommunications Infrastructure Act 2022, through the Product Security (Security Requirements for Relevant Connectable Products) Regulations 2023, has prohibited universal default and easily guessable passwords in consumer connectable products supplied to the UK market, with enforcement by the Office for Product Safety and Standards. The requirement mirrors provision 5.1-1 of ETSI EN 303 645. Internationally, CISA’s Secure by Design pledge asks manufacturers to make the same change voluntarily.

If you want to know which of your own devices still answer to their factory login, our Penetration Test Services usually produce that list within the first day of an engagement.

FAQ – Frequently Asked Questions

Is a Unique Password Printed on the Device Good Enough?

It satisfies UK law and removes the mass-exploitation risk, because knowing one unit’s password tells you nothing about the next. It is not perfect: labels are photographed, devices are resold, and the password may be derivable if the generator is weak. Pair it with a forced change at first setup and a genuinely random value from a cryptographic source.

How Do I Find Hardcoded Credentials in a Product I Bought?

Extract the firmware and search it. Strings analysis, password hash files inside the filesystem, and review of authentication code often reveal accounts the interface never shows. Tools such as binwalk and EMBA automate much of this. If you cannot extract the image, ask the vendor directly and make the answer a contractual commitment rather than an email reply.

Why Do Vendors Still Ship Universal Defaults?

Cost and support. A single credential simplifies manufacturing, documentation, and the helpdesk script when a customer cannot log in. Per-device secrets require provisioning infrastructure and labelling at the production line. The economics only changed when regulators attached penalties, which is precisely what the UK PSTI regime and similar rules elsewhere were designed to do.

Do Default Passwords Matter on an Internal Network?

Yes, often more than on the perimeter. Internal devices rarely have monitoring, and an attacker who already has a foothold uses them to escalate, pivot, and persist. Printers and management cards hold domain service accounts; building controllers bridge into other networks. Treat every management interface as internet-facing when deciding how to protect it.

Related Terms

You May Be Interested In These

What Is ISO/IEC 27017?

Cybersecurity Terms

17 November 2026

What Is ISO/IEC 27017?

Read More
What Is a Man-in-the-Middle Attack?

Cybersecurity Terms

17 November 2026

What Is a Man-in-the-Middle Attack?

Read More