CWEweakness

CWE-309 Use of Password System for Primary Authentication

High Official page ↗
Abstraction
Base
Structure
Simple
Status
Draft
Likelihood of exploit
High
Languages
Go, Not Language-Specific
CWE version
5.0

Description

The use of password systems as the primary means of authentication may be subject to several flaws or shortcomings, each reducing the effectiveness of the mechanism.

Common consequences

• Access Control: Bypass Protection Mechanism, Gain Privileges or Assume Identity — A password authentication mechanism error will almost always result in attackers being authorized as valid users.

Potential mitigations

• [Architecture and Design] In order to protect password systems from compromise, the following should be noted: • Passwords should be stored safely to prevent insider attack and to ensure that -- if a system is compromised -- the passwords are not retrievable. Due to password reuse, this information may be useful in the compromise of other systems these users work with. In order to protect these passwords, they should be stored encrypted, in a non-reversible state, such that the original text password cannot be extracted from the stored value. • Password aging should be strictly enforced to ensure that passwords do not remain unchanged for long periods of time. The longer a password remains in use, the higher the probability that it has been compromised. For this reason, passwords should require refreshing periodically, and users should be informed of the risk of passwords which remain in use for too long. • Password strength should be enforced intelligently. Rather than restrict passwords to specific content, or specific length, users should be encouraged to use upper and lower case letters, numbers, and symbols in their passwords. The system should also ensure that no passwords are derived from dictionary words. • [Architecture and Design] Use a zero-knowledge password protocol, such as SRP. • [Architecture and Design] Ensure that passwords are stored safely and are not reversible. • [Architecture and Design] Implement password aging functionality that requires passwords be changed after a certain point. • [Architecture and Design] Use a mechanism for determining the strength of a password and notify the user of weak password use. • [Architecture and Design] Inform the user of why password protections are in place, how they work to protect data integrity, and why it is important to heed their warnings.

Related

Attack pattern · CAPEC (12)

  • CAPEC-16 Dictionary-based Password Attack attack pattern
  • CAPEC-49 Password Brute Forcing attack pattern
  • CAPEC-509 Kerberoasting attack pattern
  • CAPEC-55 Rainbow Table Password Cracking attack pattern
  • CAPEC-555 Remote Services with Stolen Credentials attack pattern
  • CAPEC-560 Use of Known Domain Credentials attack pattern
  • CAPEC-561 Windows Admin Shares with Stolen Credentials attack pattern
  • CAPEC-565 Password Spraying attack pattern
  • CAPEC-600 Credential Stuffing attack pattern
  • CAPEC-652 Use of Known Kerberos Credentials attack pattern
  • CAPEC-653 Use of Known Operating System Credentials attack pattern
  • CAPEC-70 Try Common or Default Usernames and Passwords attack pattern

Child of · CWE (2)

  • CWE-1390 Weak Authentication weakness
  • CWE-654 Reliance on a Single Factor in a Security Decision weakness

Peer of · CWE (1)

  • CWE-308 Use of Single-factor Authentication weakness

Referenced by CAPEC · weakness (12)

  • CAPEC-16 Dictionary-based Password Attack attack pattern
  • CAPEC-49 Password Brute Forcing attack pattern
  • CAPEC-509 Kerberoasting attack pattern
  • CAPEC-55 Rainbow Table Password Cracking attack pattern
  • CAPEC-555 Remote Services with Stolen Credentials attack pattern
  • CAPEC-560 Use of Known Domain Credentials attack pattern
  • CAPEC-561 Windows Admin Shares with Stolen Credentials attack pattern
  • CAPEC-565 Password Spraying attack pattern
  • CAPEC-600 Credential Stuffing attack pattern
  • CAPEC-652 Use of Known Kerberos Credentials attack pattern
  • CAPEC-653 Use of Known Operating System Credentials attack pattern
  • CAPEC-70 Try Common or Default Usernames and Passwords attack pattern

Referenced by CVE · weakness (2)

  • CVE-2026-44300 OpenCost provides cost monitoring for Kubernetes workloads and cloud costs. vulnerability
  • CVE-2024-45675 IBM Informix Dynamic Server 14.10 could allow a local user on the system to log into the Informix server as administrator without a… vulnerability

Referenced by CWE · has member (1)

  • CWE-1468 Weaknesses Addressed by the OWASP Golang Secure Coding Practices Guide view

Referenced by CWE · peer of (2)

  • CWE-262 Not Using Password Aging weakness
  • CWE-308 Use of Single-factor Authentication weakness

Referenced by OWASP · mapped cwe (1)

  • A07:2025 Authentication Failures Top 10 2025