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/awardeco-0.2/src/awardeco.c Examining data/awardeco-0.2/src/awardeco.h Examining data/awardeco-0.2/src/awardhlp.h Examining data/awardeco-0.2/src/awardsft.h Examining data/awardeco-0.2/src/awardver.h Examining data/awardeco-0.2/src/awardfnc.c Examining data/awardeco-0.2/src/kernel.c FINAL RESULTS: data/awardeco-0.2/src/awardfnc.c:170:40: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. if((atoi(Buf)>=0) && (atoi(Buf)<70)) sprintf(Buf,"%.2s %s %s%.2s",day,Months[atoi(mon)],"20",year); data/awardeco-0.2/src/awardfnc.c:171:9: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. else sprintf(Buf,"%.2s %s %s%.2s",day,Months[atoi(mon)],"19",year); data/awardeco-0.2/src/awardeco.c:79:14: [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( (ptx = fopen(argv[1],"rb")) == NULL ) data/awardeco-0.2/src/awardfnc.c:168:3: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(Buf,"%2.2s",year); data/awardeco-0.2/src/awardfnc.c:170:7: [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). if((atoi(Buf)>=0) && (atoi(Buf)<70)) sprintf(Buf,"%.2s %s %s%.2s",day,Months[atoi(mon)],"20",year); data/awardeco-0.2/src/awardfnc.c:170:25: [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). if((atoi(Buf)>=0) && (atoi(Buf)<70)) sprintf(Buf,"%.2s %s %s%.2s",day,Months[atoi(mon)],"20",year); data/awardeco-0.2/src/awardfnc.c:170:80: [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). if((atoi(Buf)>=0) && (atoi(Buf)<70)) sprintf(Buf,"%.2s %s %s%.2s",day,Months[atoi(mon)],"20",year); data/awardeco-0.2/src/awardfnc.c:171:49: [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). else sprintf(Buf,"%.2s %s %s%.2s",day,Months[atoi(mon)],"19",year); data/awardeco-0.2/src/awardfnc.c:298:17: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(Buf2,head.FileName,head.FilenameLen); data/awardeco-0.2/src/awardfnc.c:301:13: [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((pto = fopen(Buf2,"wb")) == NULL) { data/awardeco-0.2/src/awardfnc.c:336:3: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(Buf,"%.12s.lzh", head.FileName); data/awardeco-0.2/src/awardfnc.c:338:13: [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((pto = fopen(Buf,"wb")) == NULL) { data/awardeco-0.2/src/awardfnc.c:366:13: [2] (tmpfile) tmpfile: Function tmpfile() has a security flaw on some systems (e.g., older System V systems) (CWE-377). if((pto = tmpfile()) == NULL) { data/awardeco-0.2/src/awardfnc.c:519:17: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(Buf2, awdhead.FileName, awdhead.FilenameLen); data/awardeco-0.2/src/awardfnc.c:522:13: [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((pto = fopen(Buf2, "wb")) == NULL) { data/awardeco-0.2/src/kernel.c:49:10: [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. unsigned char c_len[NC], pt_len[NPT]; data/awardeco-0.2/src/kernel.c:130:48: [1] (buffer) getc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). compsize--; subbitbuf = (unsigned char) getc(infile); ANALYSIS SUMMARY: Hits = 17 Lines analyzed = 1314 in approximately 0.05 seconds (26952 lines/second) Physical Source Lines of Code (SLOC) = 948 Hits@level = [0] 78 [1] 1 [2] 14 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 95 [1+] 17 [2+] 16 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 100.211 [1+] 17.9325 [2+] 16.8776 [3+] 2.1097 [4+] 2.1097 [5+] 0 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.