C++ detectors
Showing all detectors for the C++ language.
Browse by tags
Browse all detectors by tags.
Browse by severity
Browse all detectors by severity.
Browse by category
Browse all detectors by category.
Browse all detectors
Disabling the HTML autoescape mechanism exposes your web applications to attacks.
Insufficiently random generators (or hardcoded seeds) can make pseudorandom sequences predictable.
Missing default
in switch
can lead to unintended bugs.
Unsafe file extensions like .exe
or .vbs
can execute code without consent.
if set(e)gid() is called after set(e)uid(), it can regain elevated group privileges.
Out of bounds read can allow attackers to read sensitive information from other memory locations or cause a crash.
Out-of-bounds write vulnerability occurs when software attempts to write data beyond the allocated memory bounds, potentially leading to memory corruption and security risks.
A thread safety violation might indicate a data race which can put the system into an inconsistent state.
Pointer subtraction allows unintended behavior.
Concurrent execution using shared resource with improper synchronization.
Use of insecure functions can lead to buffer overflow.
Use of sizeof on a malloced pointer type is incorrect.
Instances of incorrect pointer scaling detected, potentially leading to unexpected behavior and vulnerabilities.
Weak file permissions can lead to privilege escalation.
Sensitive information should not be exposed through log files or stack traces.
Missing authorization checks can lead to unauthorized access to a resource or performance of an action.
A function returns the address of a stack variable will cause unintended program behavior, typically in the form of a crash.
Improper neutralization of special elements used in an OS command ('OS Command Injection')
Using memory after it has been freed can lead to unexpected behavior or exploitation.
Secure comparison type safety recommendation.
Off-by-one errors occur when a loop or array index is incorrectly incremented or decremented by one, leading to unintended behavior.
Creating file paths from untrusted input might give a malicious actor access to sensitive files.
Insecure ways of creating temporary files and directories can lead to race conditions, privilege escalation, and other security vulnerabilities.
Use of insecure cryptography.
Connections that use insecure protocols transmit data in cleartext, which can leak sensitive information.
Dereferencing an unchecked value without verification, leading to potential runtime errors or undefined behavior.
Use of untrusted inputs in SQL database query can enable attackers to read, modify, or delete sensitive data in the database.
Missing checks might cause silent failures that are harder to debug.
Improper restriction of operations within the bounds of a memory buffer.
Repeatedly locking critical resources in a concurrent environment can lead to varied consequences.
Improper input validation can enable attacks and lead to unwanted behavior.
Dereferencing a null pointer can lead to unexpected null pointer exceptions.
Redundant data copying operations in the code lead to performance and memory inefficiencies.
Improper certificate validation might allow an attacker to spoof a trusted entity by interfering in the communication path between the host and client.
Improper authentication from insufficient identity verification.