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/python-systemd-234/systemd/_daemon.c Examining data/python-systemd-234/systemd/_journal.c Examining data/python-systemd-234/systemd/_reader.c Examining data/python-systemd-234/systemd/id128-constants.h Examining data/python-systemd-234/systemd/id128-defines.h Examining data/python-systemd-234/systemd/id128.c Examining data/python-systemd-234/systemd/login.c Examining data/python-systemd-234/systemd/macro.h Examining data/python-systemd-234/systemd/pyutil.c Examining data/python-systemd-234/systemd/pyutil.h Examining data/python-systemd-234/systemd/strv.c Examining data/python-systemd-234/systemd/strv.h Examining data/python-systemd-234/systemd/util.c Examining data/python-systemd-234/systemd/util.h FINAL RESULTS: data/python-systemd-234/systemd/util.c:68:13: [4] (race) access: This usually indicates a security flaw. If an attacker can change anything along the path between the call to access() and the file's actual use (e.g., by moving files), the attacker can exploit the race condition (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid()) and try to open the file directly. if (access("/proc/net/if_inet6", F_OK) != 0) data/python-systemd-234/systemd/util.c:92: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). if (strlen(s) > IF_NAMESIZE-1) ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 3082 in approximately 0.10 seconds (30796 lines/second) Physical Source Lines of Code (SLOC) = 2295 Hits@level = [0] 0 [1] 1 [2] 0 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 2 [1+] 2 [2+] 1 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 0.87146 [1+] 0.87146 [2+] 0.43573 [3+] 0.43573 [4+] 0.43573 [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.