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/blueman-2.1.4/module/libblueman.c
Examining data/blueman-2.1.4/module/libblueman.h
Examining data/blueman-2.1.4/module/modem-prober.c
Examining data/blueman-2.1.4/module/modem-prober.h

FINAL RESULTS:

data/blueman-2.1.4/module/libblueman.c:132:9:  [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(ifr.ifr_name, name, IFNAMSIZ);
data/blueman-2.1.4/module/modem-prober.c:147: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[SERIAL_BUF_SIZE + 1];
data/blueman-2.1.4/module/modem-prober.c:471:7:  [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).
	fd = open (device, O_RDWR | O_EXCL | O_NONBLOCK);
data/blueman-2.1.4/module/libblueman.c:54:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(ifr.ifr_name, iface, IFNAMSIZ);
data/blueman-2.1.4/module/libblueman.c:153:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(req.ifr_name, name, IFNAMSIZ);
data/blueman-2.1.4/module/modem-prober.c:82:18:  [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).
	for (i = 0; i < strlen (cmd) && eagain_count > 0;) {
data/blueman-2.1.4/module/modem-prober.c:109:43:  [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).
		if (!strncasecmp (line, terminators[i], strlen (terminators[i])))
data/blueman-2.1.4/module/modem-prober.c:157:16:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		bytes_read = read (fd, buf, SERIAL_BUF_SIZE);
data/blueman-2.1.4/module/modem-prober.c:179:16:  [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).
				if (tmp && strlen (tmp)) {
data/blueman-2.1.4/module/modem-prober.c:190:17:  [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).
					if (tmp && strlen (tmp)) {
data/blueman-2.1.4/module/modem-prober.c:220:24:  [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).
	const char *p = buf + strlen (GCAP_TAG);
data/blueman-2.1.4/module/modem-prober.c:247:24:  [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).
	const char *p = buf + strlen (GMM_TAG);

ANALYSIS SUMMARY:

Hits = 12
Lines analyzed = 1115 in approximately 0.11 seconds (10119 lines/second)
Physical Source Lines of Code (SLOC) = 831
Hits@level = [0]   3 [1]   9 [2]   3 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  15 [1+]  12 [2+]   3 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 18.0505 [1+] 14.4404 [2+] 3.61011 [3+]   0 [4+]   0 [5+]   0
Dot directories skipped = 3 (--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.