Amazon Q
Detector Library
C detectors (38/38)
Logging of sensitive informationInsecure Use Of ChrootDeadlock And Lock InconsistencyUnsafe File ExtensionNumeric Truncation ErrorOS command injectionIncorrect Use Of FreeInsecure Use strcat fnSQL injectionBitwise Operator On Signed OperandInsecure use gets fnRandom fd exhaustionHardcoded CredentialsRedundant Free UsageIncorrect default PermissionsInsecure Use MemsetDivide By Zero.Return Stack AddressUnchecked Return ValueIncorrect Format SpecifierPath traversalImproper Input ValidationImproper Null TerminationOut Of Bounds ReadInteger OverflowInsecure use strtok functionImproper size of a memory bufferUnused Assigned Variablesincomplete-cleanupNull pointer dereferenceInsecure Temporary File Or DirectoryInsecure Buffer AccessIncorrect Use Ato FnLoose File PermissionsCross-site Scripting.Exposure of Sensitive InformationOut-of-bounds WriteString Equality
Security detectors
Logging of sensitive information
Sensitive information has been logged in your code which may leads to sensitive information leak.
Insecure Use Of Chroot
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.Deadlock And Lock Inconsistency
This code contains a potential deadlock and violates lock consistency due to incorrect lock ordering or nested locking.
Unsafe File Extension
Insufficiently restrictive file uploads can lead to inadvertently running malicious code.
Numeric Truncation Error
This code contains a potential format vulnerability due to the use of function without specifying correct format specifier.
OS command injection
Constructing operating system or shell commands with unsanitized user input can lead to inadvertently running malicious code.
Incorrect Use Of Free
Using memory after it has been freed can lead to unexpected behavior or exploitation.
Insecure Use strcat fn
strcat or strncat can lead to buffer overflow vulnerabilities.
SQL injection
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 On Signed Operand
Bitwise operator applied on signed operand.
Insecure use gets fn
gets can lead to buffer overflow vulnerabilities.
Random fd exhaustion
Failure to limit and close open file descriptors allows uncontrolled resource consumption which can crash programs or degrade system performance.
Hardcoded Credentials
Credentials are hardcoded.
Redundant Free Usage
Calling free method twice can be vulnerable to memory location.
Incorrect default Permissions
Incorrect default permissions, potentially exposing the resource to unauthorized access.
Insecure Use Memset
Calling memset method can leave sensitive information behind.
Divide By Zero.
Software flaws related to dividing by zero.
Return Stack Address
A function returns the address of a stack variable will cause unintended program behavior, typically in the form of a crash.
Unchecked Return Value
Check the return value from a method or function.
Incorrect Format Specifier
This code contains a potential format vulnerability due to the use of function without specifying correct format specifier.
Path traversal
Creating file paths from untrusted input might give a malicious actor access to sensitive files.
Improper Input Validation
Improper input validation can enable attacks and lead to unwanted behavior.
Improper Null Termination
Improper null termination of a string while using string manipulation functions (memset, strncpy, etc).
Out Of Bounds Read
Out of bounds read can allow attackers to read sensitive information from other memory locations or cause a crash.
Integer Overflow
An integer overflow might might cause security issues when it is used for resource management or execution control.
Insecure use strtok function
strtok() can cause unintended consequences and security issues.
Improper size of a memory buffer
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.
Unused Assigned Variables
The variable's value is assigned but never used, making it a dead store.
incomplete-cleanup
This concept often emphasizes identifying instances in code where resources, like file descriptors, aren't properly
released or closed, particularly in C programming.Null pointer dereference
We observed that a NULL pointer dereference occurs when a program attempts to access the value referenced by a pointer that is currently set to NULL.
Insecure Temporary File Or Directory
Securely create temporary files using functions like mkstemp() or tmpfile(), ensuring proper permissions with open() or fopen() during creation or via chmod() afterward.
Insecure Buffer Access
Use of insecure function can lead to buffer overflows.
Incorrect Use Ato Fn
Use
strtol() instead of atoi() for string to number conversions to avoid undefined behavior from invalid inputs.Loose File Permissions
Providing permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Cross-site Scripting.
Improper Neutralization of Input During Web Page Generation.
Exposure of Sensitive Information
This code transmits sensitive information over a network or communication channel in cleartext, making it vulnerable to interception by attackers.
Out-of-bounds Write
Out of bounds write can allow attackers to write sensitive information from other memory locations or cause a crash.