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/bustle-0.8.0/c-sources/pcap-reader.c
Examining data/bustle-0.8.0/c-sources/pcap-monitor.c
Examining data/bustle-0.8.0/c-sources/bustle-pcap.c
Examining data/bustle-0.8.0/c-sources/pcap-reader.h
Examining data/bustle-0.8.0/c-sources/pcap-monitor.h
Examining data/bustle-0.8.0/c-sources/config.h

FINAL RESULTS:

data/bustle-0.8.0/c-sources/pcap-monitor.c:889: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 sname[PATH_MAX] = { 0 };
data/bustle-0.8.0/c-sources/pcap-monitor.c:893:18:  [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 pt_slave = open (sname, O_RDWR);
data/bustle-0.8.0/c-sources/pcap-reader.c:231: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 errbuf[PCAP_ERRBUF_SIZE] = {0};

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 1699 in approximately 0.10 seconds (17863 lines/second)
Physical Source Lines of Code (SLOC) = 1159
Hits@level = [0]  10 [1]   0 [2]   3 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  13 [1+]   3 [2+]   3 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 11.2166 [1+] 2.58844 [2+] 2.58844 [3+]   0 [4+]   0 [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.