Weak password meaning, in plain words

A weak password is short and simple enough to be guessed or brute-forced quickly. What the Japanese government, NIST SP 800-63B-4 and CWE-521 say about length.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

A weak password is a short, simple password that can be broken quickly by guessing or brute force. MITRE's CWE-521 organizes, as "weak password requirements", the weakness in which a product does not require users to have strong passwords. Both how the service is built and how users choose passwords are involved.

How do weak passwords work?

Consider a bicycle dial lock set to "0000". The lock is on, but it opens just by turning through the numbers in order. With a password, if the string is easy to guess or short, the same thing happens.

The Ministry of Internal Affairs and Communications' "Setting and managing secure passwords" lists examples to avoid. They are a string identical to the ID, the user's own information such as name, phone number or date of birth, a single dictionary word in English, repeated characters, and sequences such as "123456" and "qwerty". The ideal, it says, is a reasonably long random string of characters.

For the service side's criteria, NIST's guidelines (SP 800-63B-4) are a useful reference. They ask for 15 characters or more when a password is used alone for authentication, and 8 characters or more when it is used as part of multi-factor authentication. They also ask for checks against commonly used values and leaked values. The problem of reuse piling on top is covered on the password reuse page. The settings behind your own login screen are a topic for a free consultation.

Why do weak passwords matter?

A password is the key to the entrance of a site. A key that cannot withstand guessing or brute force cannot guard the entrance. On a site with a member login screen or an admin screen, the keys of both users and operators are at stake.

NIST's guidelines also say that services should not impose composition rules such as mixing character types, and should not require regular changes. Rather than forcing complexity, they put weight on length and on avoiding commonly used values. However, if there is evidence of a leak, a change is required.

MITRE's CWE-521 lists, as countermeasures, minimum and maximum lengths, limits on reuse, and avoiding commonly used passwords and context strings such as the ID. It also recommends adding a second authentication factor so as not to rely on the password alone.

Related terms

  • Brute-force attack: an attack that tries passwords one after another automatically in an attempt to break in.
  • Dictionary attack: an attack that breaks passwords using a list of commonly used words.
  • Password reuse: using the same password on several services.

Next step

To review member logins and admin screens, including the password standard, contact us. The free URL check shows how a public login page looks from outside, such as its encryption, and it cannot test passwords.

Frequently asked questions

Does mixing in symbols make a strong password?

Mixing is not enough. NIST's guidelines ask services not to impose composition rules such as mixing character types. Instead, they list length, and a check that the password is not a commonly used one.

Should passwords be changed regularly?

When there is no fact of a leak or takeover, regular changes are not required. The Ministry of Internal Affairs and Communications says regular changes are unnecessary, and NIST's guidelines also do not require regular changes. Change the password at once when a leak is found.

Frequently asked questions

Does mixing in symbols make a strong password?

Mixing is not enough. NIST's guidelines ask services not to impose composition rules such as mixing character types. Instead, they list length, and a check that the password is not a commonly used one.

Should passwords be changed regularly?

When there is no fact of a leak or takeover, regular changes are not required. The Ministry of Internal Affairs and Communications says regular changes are unnecessary, and NIST's guidelines also do not require regular changes. Change the password at once when a leak is found.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.