Authentication and Sessions Findings.
32 findings in authentication and session handling, each written up as a report carries it: what the weakness is and what it lets an attacker do, the fix, CVSS 3.1 and 4.0 ratings, the CWE and the references.
Critical5
Default or Well-Known CredentialsCVSS 9.8 · CWE-1392A system still accepts a vendor default or widely published username and password, so anyone who knows the product can sign in with it.Authentication BypassCVSS 9.1 · CWE-288Protected functions or data can be reached without valid credentials, because the authentication check can be skipped or deceived.JWT Algorithm ConfusionCVSS 9.1 · CWE-347The application lets a token's own header choose how it is verified, so an attacker can sign tokens using the public key as an HMAC secret, or send them with no signature.JWT Signature Not VerifiedCVSS 9.1 · CWE-347The application accepts JSON Web Tokens without checking their signature, so anyone can change the claims in a token, such as the user ID or role, and the change is trusted.SAML Response Signature Not ValidatedCVSS 9.1 · CWE-347The service provider accepts SAML responses or assertions without properly validating their signature, so an attacker can forge or alter an assertion and sign in as any user.
High9
Weak or Guessable Passwords in UseCVSS 8.2 · CWE-521Accounts use passwords that are common, short or follow predictable patterns, so an attacker can sign in by trying a few likely values.JWT Signed With a Weak SecretCVSS 8.1 · CWE-1391JSON Web Tokens are signed with an HMAC secret that is short or guessable, so it can be recovered offline from any valid token and used to forge new ones.OAuth Redirect URI Not ValidatedCVSS 8.1 · CWE-601The OAuth or OpenID Connect authorisation server does not strictly check the redirect URI, so a crafted link can send a user's authorisation code or token to an attacker.Password Reset Link PoisoningCVSS 8.1 · CWE-640Password reset emails build their link from the request's Host header, so an attacker can make a victim's genuine reset email point to a server they control.Insecure Password Reset MechanismCVSS 7.4 · CWE-640The password reset process can be abused to take over other users' accounts, for example through guessable, reusable or misdirected reset tokens.Passwords Stored in Plain Text or Reversible FormCVSS 7.4 · CWE-257User passwords are stored as plain text, in an encoding, or encrypted with a key the application holds, so anyone who reads the store and key can recover every password.Predictable Session IdentifiersCVSS 7.4 · CWE-330Session identifiers are generated in a way that lets an attacker predict or guess values issued to other users, and so take over their sessions.Weak Password HashingCVSS 7.4 · CWE-916User passwords are stored with a fast or unsalted hash such as MD5, SHA-1 or SHA-256, so they can be recovered quickly by offline cracking from a copy of the database.Multi-Factor Authentication BypassCVSS 7.1 · CWE-304The second authentication factor can be skipped, guessed or defeated, so an attacker who knows a user's password can sign in without it.
Medium11
Insecure Persistent Login TokenCVSS 6.8 · CWE-539The 'remember me' cookie that keeps users signed in is built from guessable or recoverable values, lasts too long or is never revoked, so a stolen or forged token gives lasting access.Sensitive Account Changes Without Re-AuthenticationCVSS 6.8 · CWE-620A signed-in session can change the password, email address or multi-factor settings without the current password, so anyone holding the session can take the account over for good.Session FixationCVSS 6.8 · CWE-384The application keeps the same session identifier after login, so an attacker who plants an identifier in a victim's browser can use the session once they sign in.Session Token in URLCVSS 6.8 · CWE-598Session identifiers or authentication tokens are placed in URLs, where they leak into logs, browser history and Referer headers.Multi-Factor Authentication Not EnforcedCVSS 6.5 · CWE-308Users can sign in with a password alone, so a stolen, guessed or reused password is enough to take over an account.No Account Lockout or Login Rate LimitingCVSS 6.5 · CWE-307The login function allows unlimited password attempts, so an attacker can guess passwords at speed without being slowed or blocked.Weak Password PolicyCVSS 6.5 · CWE-521The application lets users choose short, common or breached passwords, which makes accounts easier to guess online or crack offline.Credentials Transmitted Over an Unencrypted ChannelCVSS 5.9 · CWE-523Usernames, passwords or authentication tokens are sent without encryption, so anyone able to observe the traffic can capture them.Password Returned in Application ResponsesCVSS 5.9 · CWE-201The application sends a user's current password, or its hash, back in pages or API responses, where it can be read from the browser, caches, logs or intercepting tools.OAuth Flow Without a State ParameterCVSS 5.4 · CWE-352The OAuth client does not bind the sign-in response to the user's browser with a state value, so an attacker can make a victim complete a sign-in or account link of the attacker's choosing.Username EnumerationCVSS 5.3 · CWE-204The application responds differently to valid and invalid usernames, letting an attacker build a list of real accounts to target.
Low6
Excessive Session TimeoutCVSS 3.7 · CWE-613Sessions stay valid through long periods of inactivity or without any overall limit, extending the time a stolen or unattended session can be used.JWT Without Expiry or With an Excessive LifetimeCVSS 3.7 · CWE-613JSON Web Tokens have no expiry or stay valid for a long time and cannot be revoked, so a stolen token remains usable for days, months or indefinitely.Sensitive Data in JWT PayloadCVSS 3.7 · CWE-201JSON Web Tokens carry personal data, internal details or secrets in their payload, which is only encoded, not encrypted, so anyone who sees a token can read them.Session Not Invalidated on LogoutCVSS 3.7 · CWE-613Logging out does not end the session on the server, so a session token captured earlier keeps working after the user has logged out.OAuth Authorisation Code Flow Without PKCECVSS 3.1 · CWE-294The OAuth authorisation code flow is used without Proof Key for Code Exchange, so an intercepted or leaked authorisation code can be redeemed or injected by someone else.OAuth Implicit Flow in UseCVSS 3.1 · CWE-522The application obtains OAuth access tokens through the implicit flow, which returns them in the browser's address bar, where they are easier to leak, steal or inject.
Informational1
The Other Areas
Web Applications 87APIs 16TLS and Certificates 20Network Services 56Internal Networks 9Active Directory 44Windows and Linux Hosts 29Patching and Outdated Software 36AWS 19Azure and Microsoft 365 19Google Cloud 11Containers and Kubernetes 17Mobile Applications 22Wireless 11Email and DNS 11Thick Clients 11Source Code and Supply Chain 13AI and LLM Applications 8Social Engineering and Physical 14IoT and OT 5