324 – Control redirects

Summary

Redirects must be controlled, especially when they depend on external input.

Description

Systems must guarantee that all redirects lead to a controlled or trusted site. In general, redirects based on input data should be avoided as they could enable phishing attacks. If they are required, they should be controlled so that users are only redirected to trusted sites.

Supported In

Essential: True

Advanced: True

References

• CAPEC-161. Infrastructure manipulation
• CWE-601. URL redirection to untrusted site ("open redirect")
• CWE-918. Server-side request forgery (SSRF)
• CWE-1022. Use of web link to untrusted target with window.opener access
• OWASP10-A10. Server-side request forgery
• CERTJ-IDS17-J. Prevent XML External Entity attacks
• CMMC-AC_L1-3_1_20. External connections
• HITRUST-01_j. User authentication for external connections
• WASC-A_38. URL redirector abuse
• ISSAF-V_10. Application security - Source code auditing (Cross Site Scripting XSS)
• MVSP-2_2. Application design controls - HTTPS only
• OWASPSCP-1. Input validation
• OWASPSCP-12. File management
• CWE25-918. Server-side request forgery (SSRF)
• ASVS-5_1_5. Input validation
• ASVS-5_2_6. Sanitization and sandboxing
• ASVS-12_6_1. SSRF protection
• SANS25-19. Server-side request forgery (SSRF)
• CASA-5_1_5. Input Validation
• CASA-5_2_6. Sanitization and Sandboxing
• OWASPMASVS-CODE-4. The app validates and sanitizes all untrusted inputs
• OWASPAPI-API7. Server Side Request Forgery
• OWASPAPI-API10. Unsafe Consumption of APIs

Weaknesses

• 100 – Server-side request forgery (SSRF)
• 156 – Uncontrolled external site redirect
• 023 – Uncontrolled external site redirect - Host Header Injection
• 097 – Reverse tabnabbing

Last updated

2024/02/05