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 use gets fn High
gets does not consider buffer boundaries and can lead to buffer overflows.
Detector ID
c/insecure-use-gets-fn@v1.0
Category
Common Weakness Enumeration (CWE) 
Tags
-
Noncompliant example
1#include <stdio.h>
2#include <string.h>
3
4int DST_BUFFER_SIZE = 120;
5
6int insecureUseGetsFnNonCompliant() {
7 char str[DST_BUFFER_SIZE];
8 // Noncompliant: gets is insecure
9 gets(str);
10 printf("%s", str);
11 return 0;
12}
Compliant example
1#include <stdio.h>
2#include <string.h>
3
4int insecureUseGetsFnCompliant() {
5 char buf[10];
6 printf("Enter text: ");
7 // Compliant: Secure funcion used with specifying size limit
8 fgets(buf, sizeof(buf), stdin);
9 return 0;
10}