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/tmfs-3/src/getattr.cc
Examining data/tmfs-3/src/read.cc
Examining data/tmfs-3/src/readdir.cc
Examining data/tmfs-3/src/get_real_path.cc
Examining data/tmfs-3/src/main.cc

FINAL RESULTS:

data/tmfs-3/src/read.cc:10: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(real_path.c_str(), O_RDONLY);

ANALYSIS SUMMARY:

Hits = 1
Lines analyzed = 143 in approximately 0.03 seconds (4523 lines/second)
Physical Source Lines of Code (SLOC) = 100
Hits@level = [0]   1 [1]   0 [2]   1 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   2 [1+]   1 [2+]   1 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+]  20 [1+]  10 [2+]  10 [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.