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/cjet-0.8.9/symbol.h Examining data/cjet-0.8.9/capsl.h Examining data/cjet-0.8.9/cjet.h Examining data/cjet-0.8.9/config.h Examining data/cjet-0.8.9/fonts.c Examining data/cjet-0.8.9/function.c Examining data/cjet-0.8.9/main.c Examining data/cjet-0.8.9/misc.c Examining data/cjet-0.8.9/page.c Examining data/cjet-0.8.9/parse.c Examining data/cjet-0.8.9/pcl.h Examining data/cjet-0.8.9/pjl.c Examining data/cjet-0.8.9/raster.c Examining data/cjet-0.8.9/symbol.c Examining data/cjet-0.8.9/io.c Examining data/cjet-0.8.9/macro.c FINAL RESULTS: data/cjet-0.8.9/io.c:39:3: [4] (format) vfprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. vfprintf(outfile, format, stuff); data/cjet-0.8.9/misc.c:199:5: [4] (format) vfprintf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. vfprintf(stderr, format, stuff); data/cjet-0.8.9/main.c:90:7: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). Risk is low because the source is a constant string. strcpy(prog_name,"CJet"); data/cjet-0.8.9/raster.c:501:24: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). Risk is low because the source is a constant string. case 1 : { pat = 17; strcpy(s,"001"); break; } data/cjet-0.8.9/raster.c:504:24: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). Risk is low because the source is a constant string. case 4 : { pat = 19; strcpy(s,"010"); break; } data/cjet-0.8.9/raster.c:526: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 cmode[4]; data/cjet-0.8.9/raster.c:528:3: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). Risk is low because the source is a constant string. strcpy(cmode,"000"); /* CaPSL 'pattern' condition thing */ data/cjet-0.8.9/cjet.h:55:29: [1] (buffer) fgetc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). #define get_next_char() fgetc(infile) ANALYSIS SUMMARY: Hits = 8 Lines analyzed = 5145 in approximately 0.24 seconds (21027 lines/second) Physical Source Lines of Code (SLOC) = 2937 Hits@level = [0] 38 [1] 1 [2] 5 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 46 [1+] 8 [2+] 7 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 15.6622 [1+] 2.72387 [2+] 2.38338 [3+] 0.680967 [4+] 0.680967 [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.