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/wabt-1.0.20/test/spec-wasm2c-prefix.c
Examining data/wabt-1.0.20/src/token.cc
Examining data/wabt-1.0.20/src/test-circular-array.cc
Examining data/wabt-1.0.20/src/wast-lexer.cc
Examining data/wabt-1.0.20/src/lexer-source.cc
Examining data/wabt-1.0.20/src/lexer-source-line-finder.cc
Examining data/wabt-1.0.20/src/apply-names.cc
Examining data/wabt-1.0.20/src/opcode.h
Examining data/wabt-1.0.20/src/binary-writer.cc
Examining data/wabt-1.0.20/src/decompiler.cc
Examining data/wabt-1.0.20/src/tools/wasm2c.cc
Examining data/wabt-1.0.20/src/tools/wasm-decompile.cc
Examining data/wabt-1.0.20/src/tools/spectest-interp.cc
Examining data/wabt-1.0.20/src/tools/wasm-opcodecnt.cc
Examining data/wabt-1.0.20/src/tools/wasm-objdump.cc
Examining data/wabt-1.0.20/src/tools/wasm-validate.cc
Examining data/wabt-1.0.20/src/tools/wast2json.cc
Examining data/wabt-1.0.20/src/tools/wasm2wat-fuzz.cc
Examining data/wabt-1.0.20/src/tools/wat2wasm.cc
Examining data/wabt-1.0.20/src/tools/wasm2wat.cc
Examining data/wabt-1.0.20/src/tools/wasm-interp.cc
Examining data/wabt-1.0.20/src/tools/wat-desugar.cc
Examining data/wabt-1.0.20/src/tools/wasm-strip.cc
Examining data/wabt-1.0.20/src/prebuilt/wasm2c.include.h
Examining data/wabt-1.0.20/src/prebuilt/wasm2c.include.c
Examining data/wabt-1.0.20/src/prebuilt/lexer-keywords.cc
Examining data/wabt-1.0.20/src/test-option-parser.cc
Examining data/wabt-1.0.20/src/intrusive-list.h
Examining data/wabt-1.0.20/src/lexer-source.h
Examining data/wabt-1.0.20/src/binary-reader-logging.h
Examining data/wabt-1.0.20/src/wat-writer.cc
Examining data/wabt-1.0.20/src/binary-reader-opcnt.cc
Examining data/wabt-1.0.20/src/error-formatter.h
Examining data/wabt-1.0.20/src/common.h
Examining data/wabt-1.0.20/src/generate-names.h
Examining data/wabt-1.0.20/src/lexer-source-line-finder.h
Examining data/wabt-1.0.20/src/test-literal.cc
Examining data/wabt-1.0.20/src/wast-parser.cc
Examining data/wabt-1.0.20/src/ir-util.h
Examining data/wabt-1.0.20/src/utf8.cc
Examining data/wabt-1.0.20/src/binary-reader-nop.h
Examining data/wabt-1.0.20/src/literal.cc
Examining data/wabt-1.0.20/src/shared-validator.cc
Examining data/wabt-1.0.20/src/decompiler-naming.h
Examining data/wabt-1.0.20/src/binary-reader-objdump.cc
Examining data/wabt-1.0.20/src/tracing.h
Examining data/wabt-1.0.20/src/test-filenames.cc
Examining data/wabt-1.0.20/src/wast-parser.h
Examining data/wabt-1.0.20/src/color.cc
Examining data/wabt-1.0.20/src/validator.h
Examining data/wabt-1.0.20/src/string-view.h
Examining data/wabt-1.0.20/src/tracing.cc
Examining data/wabt-1.0.20/src/binding-hash.cc
Examining data/wabt-1.0.20/src/binary.h
Examining data/wabt-1.0.20/src/binary-writer-spec.cc
Examining data/wabt-1.0.20/src/binary-reader.cc
Examining data/wabt-1.0.20/src/binary-reader-logging.cc
Examining data/wabt-1.0.20/src/binary.cc
Examining data/wabt-1.0.20/src/hash-util.h
Examining data/wabt-1.0.20/src/token.h
Examining data/wabt-1.0.20/src/leb128.h
Examining data/wabt-1.0.20/src/wast-lexer.h
Examining data/wabt-1.0.20/src/stream.h
Examining data/wabt-1.0.20/src/opcode-code-table.h
Examining data/wabt-1.0.20/src/config.cc
Examining data/wabt-1.0.20/src/c-writer.cc
Examining data/wabt-1.0.20/src/common.cc
Examining data/wabt-1.0.20/src/color.h
Examining data/wabt-1.0.20/src/binary-writer-spec.h
Examining data/wabt-1.0.20/src/binary-reader-objdump.h
Examining data/wabt-1.0.20/src/decompiler-ast.h
Examining data/wabt-1.0.20/src/expr-visitor.cc
Examining data/wabt-1.0.20/src/filenames.cc
Examining data/wabt-1.0.20/src/range.h
Examining data/wabt-1.0.20/src/literal.h
Examining data/wabt-1.0.20/src/apply-names.h
Examining data/wabt-1.0.20/src/binary-writer.h
Examining data/wabt-1.0.20/src/shared-validator.h
Examining data/wabt-1.0.20/src/make-unique.h
Examining data/wabt-1.0.20/src/error.h
Examining data/wabt-1.0.20/src/test-interp.cc
Examining data/wabt-1.0.20/src/filenames.h
Examining data/wabt-1.0.20/src/result.h
Examining data/wabt-1.0.20/src/decompiler-ls.h
Examining data/wabt-1.0.20/src/test-hexfloat.cc
Examining data/wabt-1.0.20/src/generate-names.cc
Examining data/wabt-1.0.20/src/ir.cc
Examining data/wabt-1.0.20/src/emscripten-helpers.cc
Examining data/wabt-1.0.20/src/option-parser.h
Examining data/wabt-1.0.20/src/hash-util.cc
Examining data/wabt-1.0.20/src/binding-hash.h
Examining data/wabt-1.0.20/src/type-checker.cc
Examining data/wabt-1.0.20/src/utf8.h
Examining data/wabt-1.0.20/src/interp/istream.cc
Examining data/wabt-1.0.20/src/interp/interp-util.cc
Examining data/wabt-1.0.20/src/interp/binary-reader-interp.h
Examining data/wabt-1.0.20/src/interp/interp-inl.h
Examining data/wabt-1.0.20/src/interp/binary-reader-interp.cc
Examining data/wabt-1.0.20/src/interp/interp-util.h
Examining data/wabt-1.0.20/src/interp/interp-wasi.cc
Examining data/wabt-1.0.20/src/interp/wasm.h
Examining data/wabt-1.0.20/src/interp/interp-wasi.h
Examining data/wabt-1.0.20/src/interp/interp.h
Examining data/wabt-1.0.20/src/interp/interp.cc
Examining data/wabt-1.0.20/src/interp/interp-math.h
Examining data/wabt-1.0.20/src/interp/istream.h
Examining data/wabt-1.0.20/src/interp/interp-wasm-c-api.cc
Examining data/wabt-1.0.20/src/type-checker.h
Examining data/wabt-1.0.20/src/decompiler.h
Examining data/wabt-1.0.20/src/wat-writer.h
Examining data/wabt-1.0.20/src/ir-util.cc
Examining data/wabt-1.0.20/src/binary-reader-ir.cc
Examining data/wabt-1.0.20/src/option-parser.cc
Examining data/wabt-1.0.20/src/string-view.cc
Examining data/wabt-1.0.20/src/binary-reader-ir.h
Examining data/wabt-1.0.20/src/cast.h
Examining data/wabt-1.0.20/src/feature.h
Examining data/wabt-1.0.20/src/test-string-view.cc
Examining data/wabt-1.0.20/src/expr-visitor.h
Examining data/wabt-1.0.20/src/test-wast-parser.cc
Examining data/wabt-1.0.20/src/binary-reader-opcnt.h
Examining data/wabt-1.0.20/src/c-writer.h
Examining data/wabt-1.0.20/src/type.h
Examining data/wabt-1.0.20/src/binary-reader.h
Examining data/wabt-1.0.20/src/feature.cc
Examining data/wabt-1.0.20/src/leb128.cc
Examining data/wabt-1.0.20/src/ir.h
Examining data/wabt-1.0.20/src/test-intrusive-list.cc
Examining data/wabt-1.0.20/src/opcode-code-table.c
Examining data/wabt-1.0.20/src/test-utf8.cc
Examining data/wabt-1.0.20/src/resolve-names.cc
Examining data/wabt-1.0.20/src/circular-array.h
Examining data/wabt-1.0.20/src/validator.cc
Examining data/wabt-1.0.20/src/stream.cc
Examining data/wabt-1.0.20/src/opcode.cc
Examining data/wabt-1.0.20/src/resolve-names.h
Examining data/wabt-1.0.20/src/test-binary-reader.cc
Examining data/wabt-1.0.20/src/error-formatter.cc
Examining data/wabt-1.0.20/wasm2c/wasm-rt-impl.h
Examining data/wabt-1.0.20/wasm2c/examples/rot13/main.c
Examining data/wabt-1.0.20/wasm2c/examples/fac/main.c
Examining data/wabt-1.0.20/wasm2c/examples/fac/fac.h
Examining data/wabt-1.0.20/wasm2c/examples/fac/fac.c
Examining data/wabt-1.0.20/wasm2c/wasm-rt-impl.c
Examining data/wabt-1.0.20/wasm2c/wasm-rt.h

FINAL RESULTS:

data/wabt-1.0.20/src/binary-reader-objdump.cc:183:3:  [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.
  printf("           %06" PRIzx ": %-18s %" PRIindex, offset,
data/wabt-1.0.20/src/binary-reader-objdump.cc:508:3:  [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.
  printf(" | local[%" PRIindex, local_index_);
data/wabt-1.0.20/src/binary-reader-objdump.cc:571:9:  [4] (format) vprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
        vprintf(fmt, args);
data/wabt-1.0.20/src/binary-reader-objdump.cc:1048:3:  [4] (format) vprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  vprintf(fmt, args);
data/wabt-1.0.20/src/common.h:40:25:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define WABT_FATAL(...) fprintf(stderr, __VA_ARGS__), exit(1)
data/wabt-1.0.20/src/decompiler-ls.h:135:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    if (access.byte_size &&
data/wabt-1.0.20/src/decompiler-ls.h:136:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        ((access.byte_size != byte_size) ||
data/wabt-1.0.20/src/decompiler-ls.h:137:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
         (access.type != type) ||
data/wabt-1.0.20/src/decompiler-ls.h:138:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
         (access.align != align)))
data/wabt-1.0.20/src/decompiler-ls.h:139:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access.is_uniform = false;
data/wabt-1.0.20/src/decompiler-ls.h:142:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access.is_uniform = false;
data/wabt-1.0.20/src/decompiler-ls.h:143:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access.byte_size = byte_size;
data/wabt-1.0.20/src/decompiler-ls.h:144:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access.type = type;
data/wabt-1.0.20/src/decompiler-ls.h:145:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access.align = align;
data/wabt-1.0.20/src/decompiler-ls.h:182:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      for (auto& access : var.second.accesses) {
data/wabt-1.0.20/src/decompiler-ls.h:183:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access.second.idx = idx++;
data/wabt-1.0.20/src/decompiler-ls.h:184:14:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        if (!access.second.is_uniform) {
data/wabt-1.0.20/src/decompiler-ls.h:190:43:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        auto mask = static_cast<uint64_t>(access.second.byte_size - 1);
data/wabt-1.0.20/src/decompiler-ls.h:192:27:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        if (cur_offset != access.first) {
data/wabt-1.0.20/src/decompiler-ls.h:196:23:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        cur_offset += access.second.byte_size;
data/wabt-1.0.20/src/decompiler-ls.h:218:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      for (auto& access : it->second.accesses) {
data/wabt-1.0.20/src/decompiler-ls.h:219:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        if (access.second.idx) s += ", ";
data/wabt-1.0.20/src/decompiler-ls.h:220:24:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        s += IdxToName(access.second.idx);
data/wabt-1.0.20/src/decompiler-ls.h:222:32:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        s += GetDecompTypeName(access.second.type);
data/wabt-1.0.20/src/decompiler.cc:246:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    if (!access.empty()) {
data/wabt-1.0.20/src/decompiler.cc:254:31:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        val.v.back() += "." + access;
data/wabt-1.0.20/src/interp/interp-wasm-c-api.cc:36:3:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  fprintf(stderr, "CAPI: [%s] " str, __func__, ##__VA_ARGS__)
data/wabt-1.0.20/src/literal.cc:813:5:  [4] (format) snprintf:
  If format strings can be influenced by an attacker, they can be exploited,
  and note that sprintf variations do not always \0-terminate (CWE-134). Use
  a constant for the format specification.
    snprintf(remainder_buffer, 21, "%" PRIu64, remainder);
data/wabt-1.0.20/src/stream.cc:26:21:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define ERROR0(msg) fprintf(stderr, "%s:%d: " msg, __FILE__, __LINE__)
data/wabt-1.0.20/src/stream.cc:28:3:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  fprintf(stderr, "%s:%d: " fmt, __FILE__, __LINE__, __VA_ARGS__)
data/wabt-1.0.20/src/tools/wasm-opcodecnt.cc:32:3:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  fprintf(stderr, "%s:%d: " fmt, __FILE__, __LINE__, __VA_ARGS__)
data/wabt-1.0.20/src/tracing.h:48:5:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    fprintf(stderr, format, std::forward<Args>(args)...);
data/wabt-1.0.20/test/spec-wasm2c-prefix.c:24:3:  [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, format, args);
data/wabt-1.0.20/src/color.cc:38:17:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
  char* force = getenv("FORCE_COLOR");
data/wabt-1.0.20/src/interp/interp-wasm-c-api.cc:492:7:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
  if (getenv("WASM_API_DEBUG") != nullptr) {
data/wabt-1.0.20/src/binary-reader-ir.cc:1136:5:  [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(segment->data.data(), data, size);
data/wabt-1.0.20/src/binary-reader-logging.cc:208:3:  [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[100];
data/wabt-1.0.20/src/binary-reader-logging.cc:222:3:  [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[100];
data/wabt-1.0.20/src/binary-reader-logging.cc:260:3:  [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[100];
data/wabt-1.0.20/src/binary-reader-logging.cc:268:3:  [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[100];
data/wabt-1.0.20/src/binary-reader-objdump.cc:645:3:  [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 buffer[WABT_MAX_FLOAT_HEX];
data/wabt-1.0.20/src/binary-reader-objdump.cc:653:3:  [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 buffer[WABT_MAX_DOUBLE_HEX];
data/wabt-1.0.20/src/binary-reader-objdump.cc:1423:7:  [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 buffer[WABT_MAX_DOUBLE_HEX];
data/wabt-1.0.20/src/binary-reader-objdump.cc:1429:7:  [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 buffer[WABT_MAX_FLOAT_HEX];
data/wabt-1.0.20/src/binary-reader-opcnt.cc:40:5:  [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(data_.data(), data, data_.size());
data/wabt-1.0.20/src/binary-reader-opcnt.cc:48: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(data_.data() + data_.size() - sizeof(T), &extra, sizeof(T));
data/wabt-1.0.20/src/binary-reader-opcnt.cc:102:7:  [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 buffer[WABT_MAX_FLOAT_HEX + 1];
data/wabt-1.0.20/src/binary-reader-opcnt.cc:110:7:  [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 buffer[WABT_MAX_DOUBLE_HEX + 1];
data/wabt-1.0.20/src/binary-reader.cc:253: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(out_value, state_.data + state_.offset, sizeof(T));
data/wabt-1.0.20/src/binary-writer.cc:504:3:  [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 desc[100];
data/wabt-1.0.20/src/binary-writer.cc:512:3:  [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 desc[100];
data/wabt-1.0.20/src/binary-writer.cc:1069:3:  [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 section_name[128];
data/wabt-1.0.20/src/binary-writer.cc:1186:3:  [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 desc[100];
data/wabt-1.0.20/src/binary-writer.cc:1309:7:  [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 desc[100];
data/wabt-1.0.20/src/binary-writer.cc:1558: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 desc[100];
data/wabt-1.0.20/src/color.cc:40:12:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
    return atoi(force) != 0;
data/wabt-1.0.20/src/common.cc:74:5:  [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(out_data->data() + old_size, buffer, bytes_read);
data/wabt-1.0.20/src/common.cc:97:18:  [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* infile = fopen(filename_cstr, "rb");
data/wabt-1.0.20/src/common.h:66:3:  [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 fixed_buf[WABT_DEFAULT_SNPRINTF_ALLOCA_BUFSIZE];                    \
data/wabt-1.0.20/src/common.h:151:5:  [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(&v[lane * sizeof(T)], &data, sizeof(data));
data/wabt-1.0.20/src/interp/binary-reader-interp.cc:798:5:  [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(dst_data.data.data(), src_data, size);
data/wabt-1.0.20/src/interp/interp-inl.h:655: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(out, data_.data() + offset + addend, sizeof(T));
data/wabt-1.0.20/src/interp/interp-inl.h:663: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(&val, data_.data() + offset + addend, sizeof(T));
data/wabt-1.0.20/src/interp/interp-inl.h:672: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(data_.data() + offset + addend, &val, sizeof(T));
data/wabt-1.0.20/src/interp/interp-inl.h:681: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(out, data_.data() + offset + addend, sizeof(T));
data/wabt-1.0.20/src/interp/interp-inl.h:690: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(data_.data() + offset + addend, &val, sizeof(T));
data/wabt-1.0.20/src/interp/interp-wasm-c-api.cc:1060:5:  [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(vec->data, src, size * sizeof(wasm_##name##_t));             \
data/wabt-1.0.20/src/interp/interp-wasm-c-api.cc:1066:5:  [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(out->data, vec->data, vec->size * sizeof(wasm_##name##_t));  \
data/wabt-1.0.20/src/interp/istream.cc:30: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(data_.data() + offset, &val, sizeof(val));
data/wabt-1.0.20/src/interp/istream.cc:100: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(&result, data_.data() + *offset, sizeof(T));
data/wabt-1.0.20/src/leb128.cc:93: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(dest, data, length);
data/wabt-1.0.20/src/lexer-source.cc:41:5:  [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(dest, src, read_size);
data/wabt-1.0.20/src/lexer-source.cc:62:5:  [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(out_data->data(), src, clamped.size());
data/wabt-1.0.20/src/literal.cc:175: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(out_bits, &value, sizeof(value));
data/wabt-1.0.20/src/literal.cc:463:3:  [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 buffer[Traits::kMaxHexBufferSize];
data/wabt-1.0.20/src/literal.cc:475:7:  [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(p, "inf");
data/wabt-1.0.20/src/literal.cc:478:7:  [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(p, "nan");
data/wabt-1.0.20/src/literal.cc:481:9:  [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(p, ":0x");
data/wabt-1.0.20/src/literal.cc:499: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(p, "0x");
data/wabt-1.0.20/src/literal.cc:527:7:  [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(p, "+0");
data/wabt-1.0.20/src/literal.cc:553: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(out, buffer, len);
data/wabt-1.0.20/src/literal.cc:797:3:  [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 reversed_buffer[40];
data/wabt-1.0.20/src/literal.cc:812: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 remainder_buffer[21];
data/wabt-1.0.20/src/literal.cc:816:5:  [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(&reversed_buffer[len], remainder_buffer, remainder_buffer_len);
data/wabt-1.0.20/src/stream.cc:137:16:  [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* file = fopen(filename_str.c_str(), "wb");
data/wabt-1.0.20/src/stream.cc:189: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(dst, src, size);
data/wabt-1.0.20/src/stream.cc:223:11:  [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_ = fopen(filename_str.c_str(), "wb");
data/wabt-1.0.20/src/test-hexfloat.cc:99: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 buffer[100];
data/wabt-1.0.20/src/test-hexfloat.cc: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 buffer[100];
data/wabt-1.0.20/src/test-hexfloat.cc:160: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 buffer[100];
data/wabt-1.0.20/src/test-hexfloat.cc:183: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 buffer[100];
data/wabt-1.0.20/src/test-hexfloat.cc:209: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 buffer[100];
data/wabt-1.0.20/src/test-hexfloat.cc:246: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 buffer[100];
data/wabt-1.0.20/src/test-literal.cc:803:3:  [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 buffer[128];
data/wabt-1.0.20/src/test-literal.cc:824: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 buffer[20];
data/wabt-1.0.20/src/test-literal.cc:832: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 buffer[3];
data/wabt-1.0.20/src/test-string-view.cc:216:3:  [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 buffer[10] = {0};
data/wabt-1.0.20/src/test-utf8.cc:32:3:  [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[4] = {static_cast<char>(cu0), static_cast<char>(cu1),
data/wabt-1.0.20/src/tools/spectest-interp.cc:79:58:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
                     s_thread_options.value_stack_size = atoi(argument.c_str());
data/wabt-1.0.20/src/tools/spectest-interp.cc:85:57:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
                     s_thread_options.call_stack_size = atoi(argument.c_str());
data/wabt-1.0.20/src/tools/wasm-interp.cc:92:58:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
                     s_thread_options.value_stack_size = atoi(argument.c_str());
data/wabt-1.0.20/src/tools/wasm-interp.cc:98:57:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
                     s_thread_options.call_stack_size = atoi(argument.c_str());
data/wabt-1.0.20/src/tools/wasm-opcodecnt.cc:69:52:  [2] (integer) atol:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
      [](const std::string& argument) { s_cutoff = atol(argument.c_str()); });
data/wabt-1.0.20/src/type-checker.cc:815: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(simd_data, &lane_idx, 16);
data/wabt-1.0.20/src/wast-lexer.cc:393:16:  [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 const char kCharClasses[257] = {
data/wabt-1.0.20/src/wat-writer.cc:461:7:  [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 buffer[128];
data/wabt-1.0.20/src/wat-writer.cc:471:7:  [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 buffer[128];
data/wabt-1.0.20/wasm2c/examples/fac/fac.c:32:5:  [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(&result, &mem->data[addr], sizeof(t1)); \
data/wabt-1.0.20/wasm2c/examples/fac/fac.c:40:5:  [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(&mem->data[addr], &wrapped, sizeof(t1));          \
data/wabt-1.0.20/wasm2c/examples/fac/main.c:15:11:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
  u32 x = atoi(argv[1]);
data/wabt-1.0.20/src/common.h:114:17:  [1] (buffer) equal:
  Function does not check the second iterator for over-read conditions
  (CWE-126). This function is often discouraged by most C++ coding standards
  in favor of its safer alternatives provided since C++14. Consider using a
  form of this function that checks the second iterator before potentially
  overflowing it.
    return std::equal(std::begin(v), std::end(v), std::begin(other.v));
data/wabt-1.0.20/src/common.h:444:30:  [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).
  ConvertBackslashToSlash(s, strlen(s));
data/wabt-1.0.20/src/interp/interp-inl.h:709:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  T read;
data/wabt-1.0.20/src/interp/interp-inl.h:710:44:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  CHECK_RESULT(AtomicLoad(offset, addend, &read));
data/wabt-1.0.20/src/interp/interp-inl.h:714:10:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  *out = read;
data/wabt-1.0.20/src/interp/wasm.h:110:22:  [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).
  wasm_name_new(out, strlen(s) + 1, s);
data/wabt-1.0.20/src/literal.cc:814:32:  [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).
    int remainder_buffer_len = strlen(remainder_buffer);
data/wabt-1.0.20/src/test-filenames.cc:26:21:  [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).
  size_t len = std::strlen(s);
data/wabt-1.0.20/src/test-hexfloat.cc:164: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).
      int len = strlen(buffer);
data/wabt-1.0.20/src/test-hexfloat.cc:251: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).
      int len = strlen(buffer);
data/wabt-1.0.20/src/test-literal.cc:41:31:  [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* const end = s + strlen(s);
data/wabt-1.0.20/src/test-literal.cc:92:31:  [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* const end = s + strlen(s);
data/wabt-1.0.20/src/test-literal.cc:99:31:  [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* const end = s + strlen(s);
data/wabt-1.0.20/src/test-literal.cc:110:31:  [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* const end = s + strlen(s);
data/wabt-1.0.20/src/test-literal.cc:121:31:  [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* const end = s + strlen(s);
data/wabt-1.0.20/src/test-literal.cc:132:31:  [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* const end = s + strlen(s);
data/wabt-1.0.20/src/test-literal.cc:144:44:  [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).
  ASSERT_EQ(Result::Ok, ParseUint64(s, s + strlen(s), &actual)) << s;
data/wabt-1.0.20/src/test-literal.cc:150:47:  [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).
  ASSERT_EQ(Result::Error, ParseUint64(s, s + strlen(s), &actual_bits)) << s;
data/wabt-1.0.20/src/test-literal.cc:155:48:  [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).
  ASSERT_EQ(Result::Error, ParseUint128(s, s + strlen(s), &actual)) << s;
data/wabt-1.0.20/src/test-literal.cc:161:54:  [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).
            ParseFloat(LiteralType::Hexfloat, s, s + strlen(s), &actual_bits))
data/wabt-1.0.20/src/test-literal.cc:169:54:  [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).
            ParseFloat(LiteralType::Hexfloat, s, s + strlen(s), &actual_bits))
data/wabt-1.0.20/src/test-literal.cc:176:55:  [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).
            ParseDouble(LiteralType::Hexfloat, s, s + strlen(s), &actual_bits))
data/wabt-1.0.20/src/test-literal.cc:184:55:  [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).
            ParseDouble(LiteralType::Hexfloat, s, s + strlen(s), &actual_bits))
data/wabt-1.0.20/src/test-string-view.cc:29:21:  [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).
  size_t len = std::strlen(s);
data/wabt-1.0.20/src/tools/spectest-interp.cc:469: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).
  size_t keylen = strlen(key);
data/wabt-1.0.20/src/wat-writer.cc:253: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).
  size_t len = strlen(s);

ANALYSIS SUMMARY:

Hits = 136
Lines analyzed = 57320 in approximately 1.37 seconds (41879 lines/second)
Physical Source Lines of Code (SLOC) = 45697
Hits@level = [0] 124 [1]  26 [2]  75 [3]   2 [4]  33 [5]   0
Hits@level+ = [0+] 260 [1+] 136 [2+] 110 [3+]  35 [4+]  33 [5+]   0
Hits/KSLOC@level+ = [0+] 5.68965 [1+] 2.97613 [2+] 2.40716 [3+] 0.765915 [4+] 0.722148 [5+]   0
Dot directories skipped = 2 (--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.