Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/libpam-blue-0.9.0/src/utils.h
Examining data/libpam-blue-0.9.0/src/bluescan.c
Examining data/libpam-blue-0.9.0/src/global.h
Examining data/libpam-blue-0.9.0/src/utils.c
Examining data/libpam-blue-0.9.0/src/bluepmain.c
Examining data/libpam-blue-0.9.0/src/lexer.c
Examining data/libpam-blue-0.9.0/src/parser.c
Examining data/libpam-blue-0.9.0/src/parser.h
FINAL RESULTS:
data/libpam-blue-0.9.0/src/bluepmain.c:91:5: [4] (format) syslog:
If syslog's format strings can be influenced by an attacker, they can be
exploited (CWE-134). Use a constant format string for syslog.
syslog (LOG_ERR, "Can't parse configuration file [%s]!" CONFIG_FILE);
data/libpam-blue-0.9.0/src/parser.c:670:21: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
# define YYFPRINTF fprintf
data/libpam-blue-0.9.0/src/bluescan.c:79:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str[18];
data/libpam-blue-0.9.0/src/lexer.c:536:1: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char lexerrbuff[MAXLEXERR];
data/libpam-blue-0.9.0/src/lexer.c:867:18: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
{ yylval.value = atoi(yytext); return DIGIT; }
data/libpam-blue-0.9.0/src/parser.c:970:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char const *yyarg[YYERROR_VERBOSE_ARGS_MAXIMUM];
data/libpam-blue-0.9.0/src/parser.c:987:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char yyformat[sizeof yyunexpected
data/libpam-blue-0.9.0/src/parser.c:1177:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char yymsgbuf[128];
data/libpam-blue-0.9.0/src/utils.c:160:16: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ( (yyin = fopen(CONFIG_FILE, "r")) == NULL) {
data/libpam-blue-0.9.0/src/bluepmain.c:213:57: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
msg[0].msg = (char *) malloc (sizeof (char) * (50 + strlen (user)));
data/libpam-blue-0.9.0/src/bluepmain.c:214:32: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
snprintf (msg[0].msg, 50 + strlen (user), "Scanning ... ");
data/libpam-blue-0.9.0/src/bluepmain.c:224:57: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
msg[0].msg = (char *) malloc (sizeof (char) * (50 + strlen (user)));
data/libpam-blue-0.9.0/src/bluepmain.c:225:32: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
snprintf (msg[0].msg, 50 + strlen (user), "found");
data/libpam-blue-0.9.0/src/lexer.c:648:14: [1] (buffer) getc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
(c = getc( yyin )) != EOF && c != '\n'; ++n ) \
data/libpam-blue-0.9.0/src/lexer.c:888:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
{ strncpy(lexerrbuff, yytext + 1, MAXLEXERR - 1);
data/libpam-blue-0.9.0/src/lexer.c:1661:29: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return yy_scan_bytes(yystr,strlen(yystr) );
data/libpam-blue-0.9.0/src/parser.c:851:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
# define yystrlen strlen
ANALYSIS SUMMARY:
Hits = 17
Lines analyzed = 4567 in approximately 0.17 seconds (27521 lines/second)
Physical Source Lines of Code (SLOC) = 2911
Hits@level = [0] 23 [1] 8 [2] 7 [3] 0 [4] 2 [5] 0
Hits@level+ = [0+] 40 [1+] 17 [2+] 9 [3+] 2 [4+] 2 [5+] 0
Hits/KSLOC@level+ = [0+] 13.741 [1+] 5.83992 [2+] 3.09172 [3+] 0.687049 [4+] 0.687049 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.