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/pdf2svg-0.2.3/pdf2svg.c FINAL RESULTS: data/pdf2svg-0.2.3/pdf2svg.c:141:23: [4] (format) snprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. size_t _wr_len = snprintf(svgFilenameBuffer, svgFilenameBufLen, svgFilename, pageInd + 1); data/pdf2svg-0.2.3/pdf2svg.c:134:31: [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). size_t svgFilenameBufLen = strlen(svgFilename) + 1; ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 174 in approximately 0.02 seconds (7958 lines/second) Physical Source Lines of Code (SLOC) = 114 Hits@level = [0] 4 [1] 1 [2] 0 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 6 [1+] 2 [2+] 1 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 52.6316 [1+] 17.5439 [2+] 8.77193 [3+] 8.77193 [4+] 8.77193 [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.