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/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-overview.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-utils.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-procfs.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-pstate.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-configure.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-overview.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-sysfs.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-configure.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-procfs.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-plugin.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-utils.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-sysfs.c Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-pstate.h Examining data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-plugin.h FINAL RESULTS: data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-procfs.c:55:10: [2] (misc) fopen: 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). file = fopen (filePath, "r"); data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-procfs.c:126:10: [2] (misc) fopen: 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). file = fopen (filePath, "r"); data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-procfs.c:172:12: [2] (misc) fopen: 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). file = fopen (filePath, "r"); data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-sysfs.c:109:17: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). (*intval) = atoi (contents); data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-sysfs.c:128:20: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). gint value = atoi (tokens[i]); data/xfce4-cpufreq-plugin-1.2.2/panel-plugin/xfce4-cpufreq-linux-procfs.c:143:9: [1] (buffer) sscanf: It's unclear if the %s limit in the format string is small enough (CWE-120). Check that the limit is sufficiently small, or use a different input function. sscanf (fileContent, ANALYSIS SUMMARY: Hits = 6 Lines analyzed = 2596 in approximately 0.07 seconds (36980 lines/second) Physical Source Lines of Code (SLOC) = 1694 Hits@level = [0] 2 [1] 1 [2] 5 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 8 [1+] 6 [2+] 5 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 4.72255 [1+] 3.54191 [2+] 2.95159 [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.