High
Showing all detectors for the C language with high severity.
Sensitive information has been logged in your code which may leads to sensitive information leak.
Improper use of chroot
function may allow attackers to escape the chroot jail due to relative paths still referencing resources outside the intended jail after chroot
function is called.
This code contains a potential deadlock and violates lock consistency due to incorrect lock ordering or nested locking.
Constructing operating system or shell commands with unsanitized user input can lead to inadvertently running malicious code.
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
strcat or strncat can lead to buffer overflow vulnerabilities.
The use of untrusted inputs in a SQL database query can enable attackers to read, modify, or delete sensitive data in the database.
Bitwise operator applied on signed operand.
gets can lead to buffer overflow vulnerabilities.
Failure to limit and close open file descriptors allows uncontrolled resource consumption which can crash programs or degrade system performance.
Calling free method twice can be vulnerable to memory location.
Calling memset method can leave sensitive information behind.
Software flaws related to dividing by zero.
A function returns the address of a stack variable will cause unintended program behavior, typically in the form of a crash.
Check the return value from a method or function.
This code contains a potential format vulnerability due to the use of function without specifying correct format specifier.
Encourage Purposeful Operator Usage in Codebase.
Creating file paths from untrusted input might give a malicious actor access to sensitive files.
Improper input validation can enable attacks and lead to unwanted behavior.
Out of bounds read can allow attackers to read sensitive information from other memory locations or cause a crash.
An integer overflow might might cause security issues when it is used for resource management or execution control.
strtok() can cause unintended consequences and security issues.
The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.
This concept often emphasizes identifying instances in code where resources, like file descriptors, aren't properly released
or closed
, particularly in C programming.
Securely create temporary files using functions like mkstemp() or tmpfile(), ensuring proper permissions with open() or fopen() during creation or via chmod() afterward.
Use of insecure function can lead to buffer overflows.
Providing permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
This code transmits sensitive information over a network or communication channel in cleartext, making it vulnerable to interception by attackers.
Out of bounds write can allow attackers to write sensitive information from other memory locations or cause a crash.
Use strcmp()
or strncmp()
instead of ==
and !=
for character content comparison.