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/rdfind-1.4.1/rdfind.cc
Examining data/rdfind-1.4.1/Checksum.cc
Examining data/rdfind-1.4.1/Dirlist.cc
Examining data/rdfind-1.4.1/Fileinfo.cc
Examining data/rdfind-1.4.1/Rdutil.cc
Examining data/rdfind-1.4.1/EasyRandom.cc
Examining data/rdfind-1.4.1/UndoableUnlink.cc
Examining data/rdfind-1.4.1/CmdlineParser.cc

FINAL RESULTS:

data/rdfind-1.4.1/Fileinfo.cc:44:6:  [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).
  f1.open(m_filename.c_str(), std::ios_base::in);
data/rdfind-1.4.1/Fileinfo.cc:82:5:  [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[4096];
data/rdfind-1.4.1/Fileinfo.cc:217:5:  [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 buf[buflength];
data/rdfind-1.4.1/Rdutil.cc:33:6:  [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).
  f1.open(filename.c_str(), std::ios_base::out);
data/rdfind-1.4.1/Fileinfo.cc:56:10:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      f1.read(m_somebytes.data(), SomeByteSize);
data/rdfind-1.4.1/Fileinfo.cc:61:10:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      f1.read(m_somebytes.data(), SomeByteSize);
data/rdfind-1.4.1/Fileinfo.cc:84:10:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      f1.read(buffer, sizeof(buffer));

ANALYSIS SUMMARY:

Hits = 7
Lines analyzed = 1892 in approximately 0.05 seconds (37895 lines/second)
Physical Source Lines of Code (SLOC) = 1412
Hits@level = [0]   2 [1]   3 [2]   4 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   9 [1+]   7 [2+]   4 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 6.37394 [1+] 4.95751 [2+] 2.83286 [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.