The system must not allow parameter inclusion in directory names or file paths.
A system must not allow the inclusion of directory names or files paths in its parameters. By tampering the fields associated with these parameters, an attacker may access those paths and compromise sensitive information.
This requirement is verified in following services
- CAPEC™-11. Cause web server misclassification
- CAPEC™-153. Input data manipulation
- CAPEC™-165. File manipulation
- CAPEC™-175. Code inclusion
- CWE™-22. Improper limitation of a pathname to a restricted directory ("path traversal")
- CWE™-23. Relative path traversal
- CWE™-36. Absolute path traversal
- CWE™-73. External control of file name or path
- OWASP TOP 10-A2. Cryptographic failures
- OWASP TOP 10-A3. Injection
- OWASP-M TOP 10-M8. Code tampering
- SANS 25-22. Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
- WASC-A_34. Predictable resource location
- NIST SSDF-PW_1_1. Design software to meet security requirements and mitigate security risks
- ISSAF-U_15. Web application SQL injections – Countermeasures
- PTES-6_2_3. Exploitation - Countermeasures (data execution prevention)
- PTES-7_4_4_1. Post Exploitation - Pillaging (user information on system)
- OWASP SCP-9. Communication security
- OWASP ASVS-3_1_1. Fundamental session management security
Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.