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/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.c Examining data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.h Examining data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-npriv.c FINAL RESULTS: data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-npriv.c:62:17: [5] (race) readlink: This accepts filename arguments; if an attacker can move those files or change the link content, a race condition results. Also, it does not terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach. len_str_path = readlink(str_proc, str_path, BUFSIZE-1); data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.c:267:3: [4] (shell) execl: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execl(NPRIV_PATH, NPRIV_PATH, authstr, sdevn, syspath, NULL); data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-npriv.c:81:5: [4] (shell) execl: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execl(USBAUTH_PATH, USBAUTH_PATH, argv[1], argv[2], argv[3], NULL); data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.c:248:2: [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 sdevn[32]; data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.c:277:2: [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 titleMsg[48]; data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.c:278:2: [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 detailedMsg[128]; data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-npriv.c:51:2: [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 str_proc[BUFSIZE] = {0}; data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-npriv.c:52:2: [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 str_path[BUFSIZE] = {0}; data/usbauth-notifier-1.0.1+git20190124.b308d5b/src/usbauth-notifier.c:236:3: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead. usleep(100000); ANALYSIS SUMMARY: Hits = 9 Lines analyzed = 620 in approximately 0.03 seconds (24135 lines/second) Physical Source Lines of Code (SLOC) = 382 Hits@level = [0] 19 [1] 1 [2] 5 [3] 0 [4] 2 [5] 1 Hits@level+ = [0+] 28 [1+] 9 [2+] 8 [3+] 3 [4+] 3 [5+] 1 Hits/KSLOC@level+ = [0+] 73.2984 [1+] 23.5602 [2+] 20.9424 [3+] 7.8534 [4+] 7.8534 [5+] 2.6178 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.