Summary

All system files generated dynamically must have an explicitly defined content type.

Description

This configuration ensures that the appropriate content type is included in the HTTP response headers when the file is served. Programming languages may include code to set the content type based on the nature of the dynamically generated content. Additionally, web frameworks and libraries provide mechanisms for specifying content types in a clear way.

Supported In

This requirement is verified in following services

References

• CAPEC™-242. Code injection
• OWASP TOP 10-A3. Injection
• OWASP TOP 10-A5. Security misconfiguration
• WASSEC-5_5. Extraction of dynamic content
• WASSEC-6_2_5_7. Information disclosure - Default web server files
• OWASP ASVS-11_1_4. Business logic security
• OWASP ASVS-12_3_4. File execution
• OWASP ASVS-12_5_2. File download
• OWASP ASVS-14_4_2. HTTP security headers
• OWASP API Security Top 10-API8. Security Misconfiguration
• CASA-11_1_4. Business Logic Security

Vulnerabilities

Free trial

Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.