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/kamera-20.04.2/kcontrol/kamera.h Examining data/kamera-20.04.2/kcontrol/kameradevice.h Examining data/kamera-20.04.2/kcontrol/kameraconfigdialog.h Examining data/kamera-20.04.2/kcontrol/kamera.cpp Examining data/kamera-20.04.2/kcontrol/kameraconfigdialog.cpp Examining data/kamera-20.04.2/kcontrol/kameradevice.cpp Examining data/kamera-20.04.2/kioslave/kamera.h Examining data/kamera-20.04.2/kioslave/kamera.cpp FINAL RESULTS: data/kamera-20.04.2/kioslave/kamera.cpp:1123:14: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. int size=vsnprintf(NULL, 0, format, xvalist); data/kamera-20.04.2/kioslave/kamera.cpp:1133:5: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(status, size+1, format, xvalist); data/kamera-20.04.2/kioslave/kamera.cpp:1139:5: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(status, 300, format, args); data/kamera-20.04.2/kioslave/kamera.cpp:1176:14: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. int size=vsnprintf(NULL, 0, format, xvalist); data/kamera-20.04.2/kioslave/kamera.cpp:1186:5: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(status, size+1, format, xvalist); data/kamera-20.04.2/kioslave/kamera.cpp:1192:5: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(status, 300, format, args); data/kamera-20.04.2/kioslave/kamera.cpp:188:32: [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(m_lockfile.toUtf8(),O_CREAT|O_WRONLY,0600); data/kamera-20.04.2/kioslave/kamera.cpp:267:71: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). QByteArray chunkDataBuffer = QByteArray::fromRawData(xx.text, strlen(xx.text)); \ data/kamera-20.04.2/kioslave/kamera.cpp:269:23: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). processedSize(strlen(xx.text)); \ data/kamera-20.04.2/kioslave/kamera.cpp:973:49: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). udsEntry.fastInsert(KIO::UDSEntry::UDS_SIZE,strlen(text)); ANALYSIS SUMMARY: Hits = 10 Lines analyzed = 2990 in approximately 0.13 seconds (22661 lines/second) Physical Source Lines of Code (SLOC) = 2217 Hits@level = [0] 0 [1] 3 [2] 1 [3] 0 [4] 6 [5] 0 Hits@level+ = [0+] 10 [1+] 10 [2+] 7 [3+] 6 [4+] 6 [5+] 0 Hits/KSLOC@level+ = [0+] 4.5106 [1+] 4.5106 [2+] 3.15742 [3+] 2.70636 [4+] 2.70636 [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.