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/e00compr-1.0.1/ex_read.c
Examining data/e00compr-1.0.1/cpl_conv.h
Examining data/e00compr-1.0.1/ex_write.c
Examining data/e00compr-1.0.1/ex_readcb.c
Examining data/e00compr-1.0.1/e00write.c
Examining data/e00compr-1.0.1/cpl_vsisimple.c
Examining data/e00compr-1.0.1/e00error.c
Examining data/e00compr-1.0.1/e00conv.c
Examining data/e00compr-1.0.1/e00compr.h
Examining data/e00compr-1.0.1/cpl_port.h
Examining data/e00compr-1.0.1/cpl_conv.c
Examining data/e00compr-1.0.1/cpl_error.c
Examining data/e00compr-1.0.1/ex_writecb.c
Examining data/e00compr-1.0.1/e00read.c
Examining data/e00compr-1.0.1/cpl_vsi.h
Examining data/e00compr-1.0.1/cpl_error.h

FINAL RESULTS:

data/e00compr-1.0.1/cpl_error.c:69:5:  [4] (format) vsprintf:
  Potential format string problem (CWE-134). Make format string constant.
    vsprintf(gszCPLLastErrMsg, fmt, args);
data/e00compr-1.0.1/cpl_vsisimple.c:168:15:  [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.
    nReturn = vfprintf( fp, pszFormat, args );
data/e00compr-1.0.1/e00error.c:82:5:  [4] (format) vsprintf:
  Potential format string problem (CWE-134). Make format string constant.
    vsprintf(gszE00LastErrMsg, pszFmt, args);
data/e00compr-1.0.1/e00write.c:582:5:  [4] (format) vsprintf:
  Potential format string problem (CWE-134). Make format string constant.
    vsprintf(szBuf, pszFmt, args);
data/e00compr-1.0.1/cpl_error.c:49:8:  [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.
static char gszCPLLastErrMsg[2000] = "";
data/e00compr-1.0.1/cpl_vsisimple.c:60: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).
    return( fopen( (char *) pszFilename, (char *) pszAccess ) );
data/e00compr-1.0.1/e00compr.h:115: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    szInBuf[E00_READ_BUF_SIZE]; /* compressed input buffer  */
data/e00compr-1.0.1/e00compr.h:116: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    szOutBuf[E00_READ_BUF_SIZE];/* uncompressed output buffer   */
data/e00compr-1.0.1/e00compr.h:143: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    szOutBuf[E00_WRITE_BUF_SIZE]; /* compressed output buffer */
data/e00compr-1.0.1/e00error.c:60:8:  [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.
static char gszE00LastErrMsg[2000] = "";
data/e00compr-1.0.1/e00write.c:298:13:  [2] (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). Risk is low because the source is a constant string.
            strcpy( psInfo->szOutBuf+psInfo->iOutBufPtr, "~~");
data/e00compr-1.0.1/e00write.c:312:13:  [2] (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). Risk is low because the source is a constant string.
            strcpy( psInfo->szOutBuf+psInfo->iOutBufPtr, "~ ");
data/e00compr-1.0.1/e00write.c:497:5:  [2] (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). Risk is low because the source is a constant string.
    strcpy( psInfo->szOutBuf+psInfo->iOutBufPtr, "~}");
data/e00compr-1.0.1/e00write.c:576:12:  [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.
    static char szBuf[E00_WRITE_BUF_SIZE];
data/e00compr-1.0.1/ex_readcb.c:22:15:  [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 ((fp = fopen("test.e00", "rt")) == NULL)
data/e00compr-1.0.1/ex_readcb.c:74:12:  [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.
    static char szBuf[256];
data/e00compr-1.0.1/ex_writecb.c:31:19:  [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 ((fp = fopen("test2.e00", "wt")) != NULL)
data/e00compr-1.0.1/cpl_conv.c:130:19:  [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).
                  strlen(pszString) );
data/e00compr-1.0.1/cpl_conv.c:176:15:  [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).
    nLength = strlen(pszRLBuffer);
data/e00compr-1.0.1/cpl_vsisimple.c:140:13:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    return( fgetc( fp ) );
data/e00compr-1.0.1/e00read.c:108:15:  [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).
             (strlen(psInfo->szInBuf)==79 || strlen(psInfo->szInBuf)==80) &&
data/e00compr-1.0.1/e00read.c:108:46:  [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).
             (strlen(psInfo->szInBuf)==79 || strlen(psInfo->szInBuf)==80) &&
data/e00compr-1.0.1/e00read.c:318: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).
        if (psInfo->bEOF && strlen(pszLine) == 0)
data/e00compr-1.0.1/e00read.c:357:17:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
                strncpy(psInfo->szInBuf, pszLine, E00_READ_BUF_SIZE);
data/e00compr-1.0.1/e00read.c:373:20:  [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).
            nLen = strlen(psInfo->szInBuf);
data/e00compr-1.0.1/e00write.c:452:17:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
                strncpy(psInfo->szOutBuf+ nStartOutBufPtr, 

ANALYSIS SUMMARY:

Hits = 26
Lines analyzed = 3176 in approximately 0.13 seconds (24916 lines/second)
Physical Source Lines of Code (SLOC) = 1317
Hits@level = [0]  15 [1]   9 [2]  13 [3]   0 [4]   4 [5]   0
Hits@level+ = [0+]  41 [1+]  26 [2+]  17 [3+]   4 [4+]   4 [5+]   0
Hits/KSLOC@level+ = [0+] 31.1314 [1+] 19.7418 [2+] 12.9081 [3+] 3.03721 [4+] 3.03721 [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.