CVE-2024-23823

Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.

Boundary protection at external interfaces stops unauthorized cross-domain communication allowed by permissive policies.

Vulnerability identification processes can surface permissive policy misconfigurations.

Hardened configuration baselines and reviews directly prevent permissive CSP or cross-domain policies.

Secure SDLC activities include review and testing of web security policies to avoid untrusted domains.

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.

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.

Network security policies can restrict cross-domain communication but do not specifically mandate strict CSP or cross-domain policy configuration.

Security of network services includes defining allowed endpoints, which can limit untrusted domains but does not directly address web-client policy files.

Web filtering can block untrusted domains at the network level, partially mitigating permissive cross-domain policies.

A.8.26 only requires that security requirements (including resilience against attacks such as injections) be identified and specified during development or acquisition; it does not itself enforce, implement, or configure any cross-domain policy, CSP, or domain whitelist that would stop exploitation of a permissive policy allowing untrusted domains.