CWE-1390
Weak Authentication
Description
The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.
{"xhtml:p":["Attackers may be able to bypass weak authentication faster and/or with less effort than expected."]}
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Read Application Data, Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands
CVE-2024-48445Chain: e-commerce app relies on an easily-guessable timestamp (CWE-341) in a weak authentication algorithm (CWE-1390)
CVE-2022-30034Chain: Web UI for a Python RPC framework does not use regex anchors to validate user login emails (CWE-777), potentially allowing bypass of OAuth (CWE-1390).
CVE-2022-35248Chat application skips validation when Central Authentication Service (CAS) is enabled, effectively removing the second factor from two-factor authentication
CVE-2021-3116Chain: Python-based HTTP Proxy server uses the wrong boolean operators (CWE-480) causing an incorrect comparison (CWE-697) that identifies an authN failure if all three conditions are met instead of only one, allowing bypass of the proxy authentication (CWE-1390)
CVE-2022-29965Distributed Control System (DCS) uses a deterministic algorithm to generate utility passwords
CVE-2022-29959Initialization file contains credentials that can be decoded using a "simple string transformation"
CVE-2020-8994UART interface for AI speaker uses empty password for root shell
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now