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/memdump-1.01/convert_size.c
Examining data/memdump-1.01/convert_size.h
Examining data/memdump-1.01/error.c
Examining data/memdump-1.01/error.h
Examining data/memdump-1.01/memdump.c
Examining data/memdump-1.01/mymalloc.c
Examining data/memdump-1.01/mymalloc.h

FINAL RESULTS:

data/memdump-1.01/error.c:102:3:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused).
		strcpy(op, strerror(err));
data/memdump-1.01/error.c:128:5:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    vfprintf(stderr, percentm(buf, fmt, err), ap);
data/memdump-1.01/error.c:144:5:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    vfprintf(stderr, percentm(buf, fmt, err), ap);
data/memdump-1.01/error.c:159:5:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    vfprintf(stderr, percentm(buf, fmt, err), ap);
data/memdump-1.01/error.h:16:49:  [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 PRINTFLIKE(x,y) __attribute__ ((format (printf, (x), (y))))
data/memdump-1.01/mymalloc.c:80:13:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused).
    return (strcpy(mymalloc(strlen(str) + 1), str));
data/memdump-1.01/memdump.c:345:18:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
    while ((ch = getopt(argc, argv, "b:km:p:s:v")) > 0) {
data/memdump-1.01/error.c:124: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    buf[BUFSIZ];
data/memdump-1.01/error.c:140: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    buf[BUFSIZ];
data/memdump-1.01/error.c:155: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    buf[BUFSIZ];
data/memdump-1.01/memdump.c:370:14:  [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).
		if ((map = fopen(optarg, "w")) == 0)
data/memdump-1.01/memdump.c:437:15:  [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).
    if ((fd = open(path, O_RDONLY, 0)) < 0)
data/memdump-1.01/error.c:103:9:  [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).
		op += strlen(op);
data/memdump-1.01/memdump.c:254:15:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	read_count = read(fd, buffer, todo);
data/memdump-1.01/mymalloc.c:80:29:  [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).
    return (strcpy(mymalloc(strlen(str) + 1), str));

ANALYSIS SUMMARY:

Hits = 15
Lines analyzed = 841 in approximately 0.03 seconds (27491 lines/second)
Physical Source Lines of Code (SLOC) = 402
Hits@level = [0]   7 [1]   3 [2]   5 [3]   1 [4]   6 [5]   0
Hits@level+ = [0+]  22 [1+]  15 [2+]  12 [3+]   7 [4+]   6 [5+]   0
Hits/KSLOC@level+ = [0+] 54.7264 [1+] 37.3134 [2+] 29.8507 [3+] 17.4129 [4+] 14.9254 [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.