This card is framework/language-specific. Examples include:
Beware of un-trusted data. Check buffer sizes. Do not rely on garbage collection. Use non-executable stacks when available. Avoid the use of known vulnerable functions. Properly free allocated memory. Use checksums or hashes to verify the integrity of interpreted code, libraries, executables, and configuration files. Utilize locking to prevent multiple simultaneous requests. Use a synchronization mechanism to prevent race conditions. Protect shared variables and resources from inappropriate concurrent access. Explicitly initialize all your variables and other data store. In cases where the application must run with elevated privileges, raise privileges as late as possible, and drop them as soon as possible. Make no assumptions about availability of other resources, and handle exceptions.
Lee can bypass application controls because dangerous/risky programming language functions have been used instead of safer alternatives, or there are type conversion errors, or because the application is unreliable when an external resource is unavailable, or there are race conditions, or there are resource initialization or allocation issues, or overflows can occur
Owasp ASVS (4.0): 14.1.2
Capec: 25 ,26 ,29 ,96 ,123 ,124 ,128 ,129 ,264 ,265
Owasp SCP: 194,195,196,197,198,199,200,201,202,205,206,207,208,209
Owasp Appsensor:
Safecode: 3,5,6,7,9,22,25,26,34
Loading comments 0%