URL redirects and forwards only allow whitelisted destinations, or show a warning when redirecting to potentially untrusted content.

Purpose: To understand the threat of unvalidated redirects and forwards please refer to the OWASP pages.

Solution: There shouldn’t be usually any need to perform redirects or forwards to sites or pages parametrized by the user input. In the unlikely case the functionality is needed, use a whitelisting approach to validate the user input.

Untrusted file data submitted to the application is not used directly with file I/O commands, particularly to protect against path traversal, local file include, file mime type, and OS command injection vulnerabilities.

Purpose: To understand the threat please refer to following pages:

• path traversal

• local file inclusion

• OS command injection

Solution: This is not something the devonfw platform can help with. Solution to this problem lies in the hands of system developers, who must use strong whitelisting/sanitization approaches when dealing with file paths, file names and content of untrusted data.

Files obtained from untrusted sources are scanned by antivirus scanners to prevent upload of known malicious content.

Purpose: Sometimes the attacks are so primitive, that even the antivirus can help…​

Solution: Malware scanner integration details depend on multiple things like:

• vendor of the scanner,

• what the scanner scans (HTTP stream, files),

• is the scanner accessible locally or is it an online service.

Description of the full scope of integration details is outside the scope of this guide.

Untrusted data is not used within inclusion, class loader, or reflection capabilities to prevent remote/local file inclusion vulnerabilities.

Purpose: Please refer to the OWASP pages regarding local and remote file inclusion attacks.

Solution: Treat this as an requirement to be included in your software development lifecycle, as the proper implementation lies in the hands of the developer.

Untrusted data is not used within cross-domain resource sharing (CORS) to protect against arbitrary remote content.

Purpose: Arbitrary remote content might impact the integrity of the system.

Solution: Treat this as an requirement to be included in your software development lifecycle, as the proper implementation lies in the hands of the developer.

The application code does not execute uploaded data obtained from untrusted sources.

Purpose: Execution of uploaded data might lead to remote code execution.

Solution: Treat this as an requirement to be included in your software development lifecycle, as the proper implementation lies in the hands of the developer.

Do not use Flash, Active-X, Silverlight, NACL, client-side Java or other client side technologies not supported natively via W3C browser standards.

Purpose: For example - you should not use Flash because of more than 1000 reasons.

Solution: The devonfw platform does not rely on any non-W3C technologies and the dev team should not use them either.