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/bindechexascii-0.0+20140524.git7dcd86/conv.c

FINAL RESULTS:

data/bindechexascii-0.0+20140524.git7dcd86/conv.c:212:6:  [4] (buffer) sscanf:
  The scanf() family's %s operation, without a limit specification, permits
  buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
  different input function.
					sscanf(argv[++i], "%s", hex);
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:330:6:  [4] (buffer) sscanf:
  The scanf() family's %s operation, without a limit specification, permits
  buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
  different input function.
					sscanf(argv[++i], "%s", buff);
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:350:6:  [4] (buffer) sscanf:
  The scanf() family's %s operation, without a limit specification, permits
  buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
  different input function.
					sscanf(argv[++i], "%s", buff);
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:209:6:  [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 bin[512] = {0}, hex[512] = {0};
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:323:5:  [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 buff[16];
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:343:5:  [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 buff[16];
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:297:12:  [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).
					len = strlen(in);
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:332:12:  [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).
					len = strlen(buff);
data/bindechexascii-0.0+20140524.git7dcd86/conv.c:352:12:  [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).
					len = strlen(buff);

ANALYSIS SUMMARY:

Hits = 9
Lines analyzed = 388 in approximately 0.02 seconds (20077 lines/second)
Physical Source Lines of Code (SLOC) = 282
Hits@level = [0]  75 [1]   3 [2]   3 [3]   0 [4]   3 [5]   0
Hits@level+ = [0+]  84 [1+]   9 [2+]   6 [3+]   3 [4+]   3 [5+]   0
Hits/KSLOC@level+ = [0+] 297.872 [1+] 31.9149 [2+] 21.2766 [3+] 10.6383 [4+] 10.6383 [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.