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/libkf5kmahjongg-20.08.3/kmahjonggtileset.h
Examining data/libkf5kmahjongg-20.08.3/kmahjonggbackgroundselector.h
Examining data/libkf5kmahjongg-20.08.3/kmahjonggtileset.cpp
Examining data/libkf5kmahjongg-20.08.3/kmahjonggbackground.cpp
Examining data/libkf5kmahjongg-20.08.3/kmahjonggconfigdialog.cpp
Examining data/libkf5kmahjongg-20.08.3/kmahjonggtilesetselector.cpp
Examining data/libkf5kmahjongg-20.08.3/kmahjonggconfigdialog.h
Examining data/libkf5kmahjongg-20.08.3/kmahjonggtilesetselector.h
Examining data/libkf5kmahjongg-20.08.3/kmahjonggbackground.h
Examining data/libkf5kmahjongg-20.08.3/kmahjonggbackgroundselector.cpp

FINAL RESULTS:

data/libkf5kmahjongg-20.08.3/kmahjonggbackground.cpp:111:17:  [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 (!bgfile.open(QIODevice::ReadOnly)) {
data/libkf5kmahjongg-20.08.3/kmahjonggtileset.cpp:205:22:  [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 (!tilesetfile.open(QIODevice::ReadOnly)) {

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 1211 in approximately 0.08 seconds (14974 lines/second)
Physical Source Lines of Code (SLOC) = 764
Hits@level = [0]   0 [1]   0 [2]   2 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   2 [1+]   2 [2+]   2 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 2.6178 [1+] 2.6178 [2+] 2.6178 [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.