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/kgamma5-5.19.5/xf86gammacfg/xf86gammacfg.cpp Examining data/kgamma5-5.19.5/kcmkgamma/kgamma.h Examining data/kgamma5-5.19.5/kcmkgamma/displaynumber.cpp Examining data/kgamma5-5.19.5/kcmkgamma/xf86configpath.cpp Examining data/kgamma5-5.19.5/kcmkgamma/xvidextwrap.h Examining data/kgamma5-5.19.5/kcmkgamma/gammactrl.h Examining data/kgamma5-5.19.5/kcmkgamma/displaynumber.h Examining data/kgamma5-5.19.5/kcmkgamma/kgamma.cpp Examining data/kgamma5-5.19.5/kcmkgamma/gammactrl.cpp Examining data/kgamma5-5.19.5/kcmkgamma/xvidextwrap.cpp Examining data/kgamma5-5.19.5/kcmkgamma/xf86configpath.h FINAL RESULTS: data/kgamma5-5.19.5/kcmkgamma/xf86configpath.cpp:47:13: [4] (race) access: This usually indicates a security flaw. If an attacker can change anything along the path between the call to access() and the file's actual use (e.g., by moving files), the attacker can exploit the race condition (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid()) and try to open the file directly. if ( !access( (Path = *it).c_str(), F_OK ) ) break; data/kgamma5-5.19.5/kcmkgamma/kgamma.cpp:430:10: [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). if ( f.open(QIODevice::ReadOnly) ) { ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 1496 in approximately 0.10 seconds (15586 lines/second) Physical Source Lines of Code (SLOC) = 1030 Hits@level = [0] 0 [1] 0 [2] 1 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 2 [1+] 2 [2+] 2 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 1.94175 [1+] 1.94175 [2+] 1.94175 [3+] 0.970874 [4+] 0.970874 [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.