helper_scripts.c

c.lang.security.double-free.double-free

returntocorp

Variable '$VAR' was freed twice. This can lead to undefined behavior.

c.lang.security.insecure-use-gets-fn.insecure-use-gets-fn

returntocorp

Avoid 'gets()'. This function does not consider buffer boundaries and can lead to buffer overflows. Use 'fgets()' or 'gets_s()' instead.

c.lang.security.insecure-use-printf-fn.insecure-use-printf-fn

returntocorp

Avoid using user-controlled format strings passed into 'sprintf', 'printf' and 'vsprintf'. These functions put you at risk of buffer overflow vulnerabilities through the use of format string exploits. Instead, use 'snprintf' and 'vsnprintf'.

c.lang.security.insecure-use-scanf-fn.insecure-use-scanf-fn

returntocorp

Avoid using 'scanf()'. This function, when used improperly, does not consider buffer boundaries and can lead to buffer overflows. Use 'fgets()' instead for reading input.

c.lang.security.insecure-use-strcat-fn.insecure-use-strcat-fn

returntocorp

Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead.

c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn

returntocorp

Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the program. Fix this by using strcpy_s instead (although note that strcpy_s is an optional part of the C11 standard, and so may not be available).

c.lang.security.insecure-use-strtok-fn.insecure-use-strtok-fn

returntocorp

Avoid using 'strtok()'. This function directly modifies the first argument buffer, permanently erasing the delimiter character. Use 'strtok_r()' instead.

c.lang.security.random-fd-exhaustion.random-fd-exhaustion

returntocorp

Call to 'read()' without error checking is susceptible to file descriptor exhaustion. Consider using the 'getrandom()' function.

c.lang.security.use-after-free.use-after-free

returntocorp

Variable '$VAR' was used after being freed. This can lead to undefined behavior.

returntocorp

Using == on char* performs pointer comparison, use strcmp instead

returntocorp

The second goto statement will always be executed.

returntocorp

Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions.

returntocorp

Avoid 'sscanf()' for number conversions. Its use can lead to undefined behavior, slow processing, and integer overflows. Instead prefer the 'strto*()' family of functions.

returntocorp

Use %s, %d, %c... to format your variables, otherwise this could leak information.

returntocorp

When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoid this potential vulnerability, it's recommended to use the `memset_s()` function instead. `memset_s()` is a standardized function that securely overwrites the memory with a specified value, making it more difficult for an attacker to recover any sensitive data that was stored in the buffer. By using `memset_s()` instead of `memset()`, you can help to ensure that your application is more secure and less vulnerable to exploits that rely on residual data in memory.