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/obsession-20140608/config.h Examining data/obsession-20140608/dbus-interface.c Examining data/obsession-20140608/dbus-interface.h Examining data/obsession-20140608/obsession-common.c Examining data/obsession-20140608/obsession-exit.c Examining data/obsession-20140608/obsession-logout.c Examining data/obsession-20140608/obsession.h FINAL RESULTS: data/obsession-20140608/obsession-common.c:156:3: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(buffer, "/run/%s.pid", display_manager); data/obsession-20140608/obsession-common.c:155: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 buffer[PATH_MAX]; data/obsession-20140608/obsession-common.c:159:12: [2] (misc) open: 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). int fd = open(buffer, O_RDONLY); data/obsession-20140608/obsession-common.c:169:17: [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). pid_t pid = atoi(buffer); data/obsession-20140608/obsession-common.c:175:6: [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(buffer, "/proc/%d/cmdline", pid); data/obsession-20140608/obsession-common.c:178:15: [2] (misc) open: 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). int fd = open(buffer, O_RDONLY); data/obsession-20140608/obsession-common.c:163:21: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). ssize_t length = read(fd, buffer, sizeof(buffer)); data/obsession-20140608/obsession-common.c:182:24: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). ssize_t length = read(fd, buffer, sizeof(buffer)); ANALYSIS SUMMARY: Hits = 8 Lines analyzed = 1332 in approximately 0.05 seconds (24930 lines/second) Physical Source Lines of Code (SLOC) = 955 Hits@level = [0] 0 [1] 2 [2] 5 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 8 [1+] 8 [2+] 6 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 8.37696 [1+] 8.37696 [2+] 6.28272 [3+] 1.04712 [4+] 1.04712 [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.