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/verdigris-1.0/benchmarks/compile/compile.cpp Examining data/verdigris-1.0/benchmarks/qobject/main.cpp Examining data/verdigris-1.0/benchmarks/qobject/object.cpp Examining data/verdigris-1.0/benchmarks/qobject/object.h Examining data/verdigris-1.0/benchmarks/startup/main.cpp Examining data/verdigris-1.0/src/wobjectdefs.h Examining data/verdigris-1.0/src/wobjectimpl.h Examining data/verdigris-1.0/tests/basic/tst_basic.cpp Examining data/verdigris-1.0/tests/qt/qmetamethod/tst_qmetamethod.cpp Examining data/verdigris-1.0/tests/qt/qmetaobject/tst_qmetaobject.cpp Examining data/verdigris-1.0/tests/qt/qmetaproperty/tst_qmetaproperty.cpp Examining data/verdigris-1.0/tests/qt/qobject/signalbug/signalbug.cpp Examining data/verdigris-1.0/tests/qt/qobject/signalbug/signalbug.h Examining data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp Examining data/verdigris-1.0/tests/templates/tst_templates.cpp Examining data/verdigris-1.0/tutorial/tutorial.cpp FINAL RESULTS: data/verdigris-1.0/tests/qt/qmetamethod/tst_qmetamethod.cpp:636:33: [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. QFETCH(QMetaMethod::Access, access); data/verdigris-1.0/tests/qt/qmetamethod/tst_qmetamethod.cpp:649:21: [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. QCOMPARE(method.access(), access); data/verdigris-1.0/tests/qt/qmetamethod/tst_qmetamethod.cpp:649:31: [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. QCOMPARE(method.access(), access); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2113:16: [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. QCOMPARE(m.access(), QMetaMethod::Public); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2120:16: [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. QCOMPARE(m.access(), QMetaMethod::Public); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2127:16: [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. QCOMPARE(m.access(), QMetaMethod::Protected); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2134:16: [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. QCOMPARE(m.access(), QMetaMethod::Protected); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2141:16: [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. QCOMPARE(m.access(), QMetaMethod::Private); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2148:16: [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. QCOMPARE(m.access(), QMetaMethod::Private); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2155:16: [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. QCOMPARE(m.access(), QMetaMethod::Public); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:2162:16: [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. QCOMPARE(m.access(), QMetaMethod::Public); data/verdigris-1.0/src/wobjectimpl.h:479:6: [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 stringdata[L]; data/verdigris-1.0/tests/qt/qmetaproperty/tst_qmetaproperty.cpp:189:35: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). W_PROPERTY(CustomReadObject *,read MEMBER _read) data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:3045:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). QVariant v = prop.read(&obj); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:3061:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). QVariant v = prop.read(&obj); data/verdigris-1.0/tests/qt/qobject/tst_qobject.cpp:3066:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). v = prop.read(&obj); ANALYSIS SUMMARY: Hits = 16 Lines analyzed = 15117 in approximately 0.42 seconds (36361 lines/second) Physical Source Lines of Code (SLOC) = 11879 Hits@level = [0] 5 [1] 4 [2] 1 [3] 0 [4] 11 [5] 0 Hits@level+ = [0+] 21 [1+] 16 [2+] 12 [3+] 11 [4+] 11 [5+] 0 Hits/KSLOC@level+ = [0+] 1.76783 [1+] 1.34691 [2+] 1.01019 [3+] 0.926004 [4+] 0.926004 [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.