Q
Detector Library
C detectors (34/34)
Logging of sensitive informationInsecure Use Of ChrootDeadlock And Lock InconsistencyUnsafe File ExtensionOS command injectionIncorrect Use Of FreeUse Of Uninitialized VariableInsecure Use strcat fnSQL injectionBitwise Operator On Signed OperandInsecure use gets fnRandom fd exhaustionRedundant Free UsageInsecure Use MemsetDivide By Zero.Return Stack AddressUnchecked Return ValueIncorrect Format SpecifierUnhandled Expression ResultPath traversalImproper Input ValidationOut Of Bounds ReadInteger OverflowInsecure use strtok functionImproper size of a memory bufferincomplete-cleanupNull pointer dereferenceInsecure Temporary File Or DirectoryInsecure Buffer AccessIncorrect Use Ato FnLoose File PermissionsExposure of Sensitive InformationOut-of-bounds WriteString Equality
Insecure Buffer Access High
We recommend you to avoid using insecure functions in your code. This functions, when used improperly, does not consider buffer boundaries and can lead to buffer overflows.
Detector ID
c/insecure-buffer-access@v1.0
Category
Noncompliant example
1#include <stdio.h>
2#include <string.h>
3
4int DST_BUFFER_SIZE = 120;
5
6int insecureBufferAccessNonCompliant() {
7 char str[DST_BUFFER_SIZE];
8 // Noncompliant: use of scanf function
9 scanf("%s", str);
10 printf("%s", str);
11 return 0;
12}
Compliant example
1#include <stdio.h>
2#include <string.h>
3
4void insecureBufferAccessCompliant(char* src, char* dest, int dest_size) {
5 if (strlen(src) < dest_size) {
6 // Compliant: Bounds checking
7 strcat(dest, src);
8 }
9}