Course contentsShow
← Security
Lesson 862 of 3,05218. Web Security - CSRF and Request ForgeryFree lesson

CORS Misconfiguration Vulnerabilities

Identifying common CORS misconfigurations including null origin bypasses, subdomain reflection, and overly permissive policies.

CORS Misconfiguration Vulnerabilities

You'll learn how common CORS misconfigurations can expose your web application to serious cross-origin attacks that bypass intended security restrictions.

Why CORS Misconfigurations Are Dangerous

You already know that CORS (Cross-Origin Resource Sharing) allows servers to relax the Same-Origin Policy. However, badly configured CORS policies can completely undermine your security, allowing attackers to steal sensitive data from authenticated users by making cross-origin requests from malicious sites.

Common CORS Misconfigurations

Null Origin Bypass

Some servers whitelist the null origin, thinking it's safe. Attackers can easily trigger a null origin using sandboxed iframes or data URLs:

Origin: null

If the server reflects this back with Access-Control-Allow-Origin: null, the attacker can read responses.

Subdomain Reflection

Servers that reflect any subdomain of their domain are vulnerable. If an attacker compromises attacker.example.com (perhaps via XSS), they can make requests to api.example.com and read responses:

Origin: https://attacker.example.com
Access-Control-Allow-Origin: https://attacker.example.com

Overly Permissive Wildcards

Using Access-Control-Allow-Origin: * with Access-Control-Allow-Credentials: true doesn't work (browsers block it), but some servers dynamically reflect any origin, achieving the same dangerous result.

Regex Validation Flaws

Weak origin validation like checking if the origin "contains" a trusted domain allows attackers to register trusted-domain.attacker.com and bypass checks.

Key Takeaway: CORS misconfigurations—including null origin bypasses, subdomain reflection, and overly permissive validation—can allow attackers to read sensitive cross-origin data. Always validate origins against an explicit allowlist and never blindly reflect user-controlled origin headers.