Control calls to interpreted code
Summary
Interpreted code (e.g., Javascript, CSS) must be loaded from domains controlled by the organization.
Description
Applications often use resources or have dependencies that are hosted on other servers. These resources should be hosted on domains controlled by the organization in order to prevent several types of injection attacks.
Supported In
This requirement is verified in following services
| Plan | Supported |
|---|---|
| Essential | 🔴 |
| Advanced | 🟢 |
References
- CAPEC™-19. Embedding scripts within scripts
- CAPEC™-154. Resource location spoofing
- CAPEC™-175. Code inclusion
- CAPEC™-242. Code injection
- CWE™-830. Inclusion of web functionality from an untrusted source
- OWASP TOP 10-A3. Injection
- OWASP TOP 10-A5. Security misconfiguration
- OWASP TOP 10-A8. Software and data integrity failures
- OWASP-M TOP 10-M9. Reverse engineering
- PA-DSS-5_2_1. Injection flaws, particularly SQL injection
- SANS 25-23. Improper Control of Generation of Code ('Code Injection')
- ISO/IEC 27002-8_26. Application security requirements
- NIST SSDF-PW_6_1. Configure the compilation, interpreter, and build processes to improve executable security
- OWASP ASVS-5_2_8. Sanitization and sandboxing
- OWASP API Security Top 10-API9. Improper Inventory Management
- CWE TOP 25-94. Improper Control of Generation of Code ('Code Injection')
- ISO/IEC 27001-8_26. Application security requirements
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.