CVE-2023-27388

Session content review can reveal authentication bypasses or failures in session establishment.

Assessments check authentication mechanisms for correct implementation and effectiveness, reducing successful authentication bypass attempts.

Identity providers centralize and enforce authentication mechanisms, reducing improper authentication.

Enforces correct authorization checks during the identifier assignment process.

Personnel screening, identity verification, and access-agreement requirements support reliable authentication and reduce authentication bypass opportunities.

Decoy authentication surfaces detect bypass attempts and deflect real credential attacks through observable malicious interactions.

Periodic review and update of procedures reduces incorrect authorization implementations over time.

Supervision identifies cases where authorization logic incorrectly permits unauthorized actions.

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

Mandating segregated approval and oversight for non-human identities reduces the chance that weak or orphaned credentials can be exploited for unauthorized authentication.

A.5.17 directly mandates generation of non-guessable unique secrets, secure transmission, immediate change of defaults/temporary creds, strong password enforcement, no-reuse, and compromise response, which stops most improper-authentication exploits at source; the bounded remainder is non-password authentication methods and sufficiency-of-proof cases (e.g. IA-2/IA-5 enhancements) left to other controls.

A.5.18's provisioning, revocation, review and adjustment of access rights (incl. before role changes/termination, with segregation and owner approval) directly stops incorrect authorization decisions from being exploitable in the vast majority of cases; the bounded remainder is incorrectness inside the authorization logic itself (e.g. flawed conditional or missing check) rather than rights that were wrongly granted.

Security requirements specified early and verified through testing drive the consistent implementation of authentication mechanisms, decreasing the likelihood that authentication steps are omitted or incorrectly applied.

A.8.26 explicitly requires identifying and addressing authentication-related requirements (including level of trust in identity via 8.5 and 5.17) as part of application development or acquisition, which prevents a slice of CWE-287 but leaves the dominant sufficiency-of-proof aspects (IA-2/IA-5) and many implementation defects untouched.