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/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/bulkloop/bulkloop.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/bulkloop/test.cpp
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/cdc/common/cdc-config.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/cdc/common/cdc.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/cdc/common/cdc.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/cdc/common/main.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/cdc/loopback/main-custom.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/cdc/to-uart/main-custom.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice/debugdev.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/debugdev.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/terminal.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/test.cpp
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/eeprom/firmware/eeprom.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/fx2/cpp/fx2.cpp
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/fx2/cpp/fx2.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/i2c/i2c.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/lights/lights.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/reset/fx2_c0.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/reset/reset.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/serial/serial.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/timers/timers.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/usbmon_c/test.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/usbmon_c/usbmon.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/fw/device.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/fw/fw.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/autovector.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/delay.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/eputils.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/fx2ints.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/fx2macros.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/fx2regs.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/fx2types.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/gpif.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/i2c.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/lights.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/setupdat.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/serial.h
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/delay.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/eputils.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/gpif.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/i2c.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep0ack_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep0in_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep0out_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep0ping_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep1in_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep1out_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep1ping_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep2_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep2ef_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep2ff_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep2isoerr_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep2pf_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep2ping_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep4_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep4ef_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep4ff_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep4isoerr_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep4pf_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep4ping_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep6_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep6ef_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep6ff_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep6isoerr_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep6pf_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep6ping_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep8_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep8ef_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep8ff_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep8isoerr_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep8pf_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ep8ping_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/errlimit_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/gpifdone_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/gpifwf_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/hispeed_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/ibn_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/sof_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/spare_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/sudav_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/suspend_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/sutok_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/interrupts/usbreset_isr.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/setupdat.c
Examining data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/serial.c

FINAL RESULTS:

data/hdmi2usb-fx2-firmware-0.0.0~git20151225/fw/device.c:24:9:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define printf(...)
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/fw/fw.c:29:9:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define printf(...)
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/eputils.c:26:9:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define printf(...)
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/i2c.c:30:25:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define i2c_printf(...) printf(__VA_ARGS__)
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/setupdat.c:24:9:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define printf(...)
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/terminal.c:54:11:  [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.
	unsigned char buf[512];
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/terminal.c:55:2:  [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 timebuf[32];
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/terminal.c:139: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).
	outfile = fopen("debuglog.txt", "w+");
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/debugdevice_full_duplex/test.cpp:28:11:  [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.
	unsigned char buf[256];
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/fx2/cpp/fx2.cpp:49:11:  [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).
void fx2::open(int vid,int pid,int idx) {
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/fx2/cpp/fx2.h:45:14:  [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).
        void open(int vid=VID,int pid=PID, int idx=0);
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/usbmon_c/test.c:32:11:  [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.
	unsigned char buf[512];
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/examples/serial/serial.c:76:10:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		char r=getchar();
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/include/serial.h:55:5:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
int getchar();
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/eputils.c:32:12:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    while (read < len) {
data/hdmi2usb-fx2-firmware-0.0.0~git20151225/lib/serial.c:72:5:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
int getchar() {

ANALYSIS SUMMARY:

Hits = 16
Lines analyzed = 7276 in approximately 0.22 seconds (33311 lines/second)
Physical Source Lines of Code (SLOC) = 3519
Hits@level = [0]  86 [1]   4 [2]   7 [3]   0 [4]   5 [5]   0
Hits@level+ = [0+] 102 [1+]  16 [2+]  12 [3+]   5 [4+]   5 [5+]   0
Hits/KSLOC@level+ = [0+] 28.9855 [1+] 4.54675 [2+] 3.41006 [3+] 1.42086 [4+] 1.42086 [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.