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/bmusb-0.7.5/bmusb.cpp
Examining data/bmusb-0.7.5/bmusb/bmusb.h
Examining data/bmusb-0.7.5/bmusb/fake_capture.h
Examining data/bmusb-0.7.5/fake_capture.cpp
Examining data/bmusb-0.7.5/format.cpp
Examining data/bmusb-0.7.5/main.cpp
Examining data/bmusb-0.7.5/v4l2proxy.cpp

FINAL RESULTS:

data/bmusb-0.7.5/bmusb.cpp:336:13:  [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 *fp = fopen(filename, "wb");
data/bmusb-0.7.5/bmusb.cpp:352: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 thread_name[16];
data/bmusb-0.7.5/bmusb.cpp:403:4:  [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 filename[255];
data/bmusb-0.7.5/bmusb.cpp:542:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(current_frame->data_copy + current_frame->len, start, bytes);
data/bmusb-0.7.5/bmusb.cpp:560:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(current_frame->data + current_frame->len, start, bytes);
data/bmusb-0.7.5/bmusb.cpp:754:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(current_frame->data_copy + current_frame->len, aligned_start, bytes_copied);
data/bmusb-0.7.5/bmusb.cpp:819:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(current_frame->data_copy + current_frame->len, aligned_start, bytes_copied);
data/bmusb-0.7.5/bmusb.cpp:916:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(usb->register_file + usb->current_register, buf, 4);
data/bmusb-0.7.5/bmusb.cpp:1013: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 buf[256];
data/bmusb-0.7.5/bmusb.cpp:1311:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(value, &flipped, sizeof(flipped));
data/bmusb-0.7.5/fake_capture.cpp:105:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(s, c, 16);
data/bmusb-0.7.5/fake_capture.cpp:115: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 buf[256];
data/bmusb-0.7.5/fake_capture.cpp:168: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 buf[256];
data/bmusb-0.7.5/fake_capture.cpp:242: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 thread_name[16];
data/bmusb-0.7.5/format.cpp:4: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 name[32];
data/bmusb-0.7.5/v4l2proxy.cpp:97:13:  [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).
	video_fd = open(filename, O_RDWR);

ANALYSIS SUMMARY:

Hits = 16
Lines analyzed = 2704 in approximately 0.19 seconds (14213 lines/second)
Physical Source Lines of Code (SLOC) = 2046
Hits@level = [0] 121 [1]   0 [2]  16 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+] 137 [1+]  16 [2+]  16 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 66.9599 [1+] 7.82014 [2+] 7.82014 [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.