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/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc
Examining data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.h
Examining data/libmongocrypt-1.0.4/kms-message/src/hexlify.c
Examining data/libmongocrypt-1.0.4/kms-message/src/hexlify.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_b64.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_caller_identity_request.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_crypto.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_crypto_apple.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_crypto_libcrypto.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_crypto_none.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_crypto_windows.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_decrypt_request.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_encrypt_request.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_kv_list.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_kv_list.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_b64.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_caller_identity_request.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_decrypt_request.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_encrypt_request.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_message.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_message_defines.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_request.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_request_opt.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_response.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message/kms_response_parser.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_message_private.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_port.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_port.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_request.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_request_opt.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_request_opt_private.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.h
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_response.c
Examining data/libmongocrypt-1.0.4/kms-message/src/kms_response_parser.c
Examining data/libmongocrypt-1.0.4/kms-message/src/sort.c
Examining data/libmongocrypt-1.0.4/kms-message/src/sort.h
Examining data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c
Examining data/libmongocrypt-1.0.4/kms-message/test/windows/dirent.h
Examining data/libmongocrypt-1.0.4/src/crypto/cng.c
Examining data/libmongocrypt-1.0.4/src/crypto/commoncrypto.c
Examining data/libmongocrypt-1.0.4/src/crypto/libcrypto.c
Examining data/libmongocrypt-1.0.4/src/crypto/none.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-binary-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-binary.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-buffer-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-cache-collinfo-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-cache-collinfo.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-cache-key-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-cache-key.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-cache-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-cache.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-compat.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-crypto-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-crypto.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ctx-datakey.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ctx-decrypt.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ctx-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-ctx.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-key-broker-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-key-broker.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-key-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-key.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-kms-ctx-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-kms-ctx.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-log-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-log.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-marking-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-marking.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-mutex-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-opts-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-opts.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-os-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-status-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-status.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt-traverse-util-private.h
Examining data/libmongocrypt-1.0.4/src/mongocrypt-traverse-util.c
Examining data/libmongocrypt-1.0.4/src/mongocrypt.c
Examining data/libmongocrypt-1.0.4/src/os_posix/os_mutex.c
Examining data/libmongocrypt-1.0.4/src/os_posix/os_once.c
Examining data/libmongocrypt-1.0.4/src/os_win/os_mutex.c
Examining data/libmongocrypt-1.0.4/src/os_win/os_once.c
Examining data/libmongocrypt-1.0.4/test/example-state-machine.c
Examining data/libmongocrypt-1.0.4/test/test-conveniences.c
Examining data/libmongocrypt-1.0.4/test/test-conveniences.h
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-buffer.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-cache.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-key-cache.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-key.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-kms-responses.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-local-kms.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-marking.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-status.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt.c
Examining data/libmongocrypt-1.0.4/test/test-mongocrypt.h
FINAL RESULTS:
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:99:49: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
std::string errorStringFromStatus(mongocrypt_t* crypt) {
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:101:23: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_status(crypt, status.get());
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:121:66: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
std::pair<bool, std::string> setKmsProviderOptions(mongocrypt_t* crypt,
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:134:49: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!mongocrypt_setopt_kms_provider_aws(crypt,
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:139:64: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
return std::make_pair(false, errorStringFromStatus(crypt));
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:156:55: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!mongocrypt_setopt_kms_provider_local(crypt, binary.get())) {
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:157:68: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
return std::make_pair(false, errorStringFromStatus(crypt));
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:385:58: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
std::unique_ptr<mongocrypt_t, MongoCryptDeleter> crypt(mongocrypt_new());
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:406:53: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
auto result = setKmsProviderOptions(crypt.get(), kmsProvidersOptions);
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:423:51: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!mongocrypt_setopt_schema_map(crypt.get(), BufferToBinary(schemaMapBuffer))) {
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:424:63: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
Nan::ThrowTypeError(errorStringFromStatus(crypt.get()));
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:467:53: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
MongoCrypt* class_instance = new MongoCrypt(crypt.release(), logger, cryptoHooks);
data/libmongocrypt-1.0.4/kms-message/src/kms_message.c:32:11: [4] (format) vsnprintf:
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.
(void) vsnprintf (error, size, fmt, va);
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:267:11: [4] (format) vsnprintf:
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.
n = vsnprintf (&str->str[str->len], remaining, format, args);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:50:10: [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, \
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-datakey.c:82:27: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_append_id (mongocrypt_t *crypt, bson_t *bson, mongocrypt_status_t *status)
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-datakey.c:129:26: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!_append_id (ctx->crypt, &key_doc, ctx->status)) {
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c:437:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c:442:17: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt = ctx->crypt;
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-private.h:71:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/src/mongocrypt-ctx.c:236:35: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_ctx_new (mongocrypt_t *crypt)
data/libmongocrypt-1.0.4/src/mongocrypt-ctx.c:241:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt-ctx.c:261:17: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx->crypt = crypt;
data/libmongocrypt-1.0.4/src/mongocrypt-ctx.c:736:48: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&ctx->kb, ctx->crypt);
data/libmongocrypt-1.0.4/src/mongocrypt-key-broker-private.h:98:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/src/mongocrypt-key-broker-private.h:104:74: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (_mongocrypt_key_broker_t *kb, mongocrypt_t *crypt);
data/libmongocrypt-1.0.4/src/mongocrypt-key-broker.c:21:74: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (_mongocrypt_key_broker_t *kb, mongocrypt_t *crypt)
data/libmongocrypt-1.0.4/src/mongocrypt-key-broker.c:24:16: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
kb->crypt = crypt;
data/libmongocrypt-1.0.4/src/mongocrypt-log-private.h:64:45: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
#define CRYPT_TRACE(log, msg) CRYPT_TRACEF (crypt, "%s", msg)
data/libmongocrypt-1.0.4/src/mongocrypt-log-private.h:68:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt, MONGOCRYPT_LOG_LEVEL_TRACE, "entry (%s:%d)", BSON_FUNC, __LINE__)
data/libmongocrypt-1.0.4/src/mongocrypt-log-private.h:72:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_log (crypt, \
data/libmongocrypt-1.0.4/src/mongocrypt.c:114:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/src/mongocrypt.c:117:17: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
BSON_ASSERT (crypt);
data/libmongocrypt-1.0.4/src/mongocrypt.c:126:11: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
return crypt;
data/libmongocrypt-1.0.4/src/mongocrypt.c:131:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_log_handler (mongocrypt_t *crypt,
data/libmongocrypt-1.0.4/src/mongocrypt.c:135:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:150:51: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (mongocrypt_t *crypt,
data/libmongocrypt-1.0.4/src/mongocrypt.c:158:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:227:4: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf (out, (len > max_bytes) ? "..." : "");
data/libmongocrypt-1.0.4/src/mongocrypt.c:251:45: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_schema_map (mongocrypt_t *crypt,
data/libmongocrypt-1.0.4/src/mongocrypt.c:258:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:296:53: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_local (mongocrypt_t *crypt,
data/libmongocrypt-1.0.4/src/mongocrypt.c:301:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:346:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_init (mongocrypt_t *crypt)
data/libmongocrypt-1.0.4/src/mongocrypt.c:350:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:393:34: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_status (mongocrypt_t *crypt, mongocrypt_status_t *out)
data/libmongocrypt-1.0.4/src/mongocrypt.c:395:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:415:35: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (mongocrypt_t *crypt)
data/libmongocrypt-1.0.4/src/mongocrypt.c:417:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:427:15: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
bson_free (crypt);
data/libmongocrypt-1.0.4/src/mongocrypt.c:457:47: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_crypto_hooks (mongocrypt_t *crypt,
data/libmongocrypt-1.0.4/src/mongocrypt.c:468:9: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!crypt) {
data/libmongocrypt-1.0.4/test/example-state-machine.c:260:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/example-state-machine.c:269:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1);
data/libmongocrypt-1.0.4/test/example-state-machine.c:270:26: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
if (!mongocrypt_init (crypt)) {
data/libmongocrypt-1.0.4/test/example-state-machine.c:275:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/example-state-machine.c:284:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/example-state-machine.c:296:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/example-state-machine.c:317:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/example-state-machine.c:329:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:111:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:135:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:210:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:228:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:229:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:230:42: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ret = mongocrypt_setopt_crypto_hooks (crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:238:20: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (ret, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:239:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:239:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:240:11: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
return crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:248:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:314:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:333:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:389:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:405:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:449:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:465:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:497:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:511:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:517:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:533:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:541:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:544:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:545:35: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_init (crypt), crypt, "crypto hooks required");
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:545:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_init (crypt), crypt, "crypto hooks required");
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:546:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:555:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:565:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:582:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:590:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:596:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:607:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto.c:25:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto.c:150:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto.c:158:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto.c:225:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:24:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:35:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:42:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:47:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:55:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:64:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:70:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:76:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:83:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:91:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:99:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:111:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:122:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:134:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:143:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:147:51: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_setopt_kms_provider_aws (crypt, "", -1, "", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:148:15: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:149:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:149:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:151:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:162:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:168:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:175:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:192:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-decrypt.c:201:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:32:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:66:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:74:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:82:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:91:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:100:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:109:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:117:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:125:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:132:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:144:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:151:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:161:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:168:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:178:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:185:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:195:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:202:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:212:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:219:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:229:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:236:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:246:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:255:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:265:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:274:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:284:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:293:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:303:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:312:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:324:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:331:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:340:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:349:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:357:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:375:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:381:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:390:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:399:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:410:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:418:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:425:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:432:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:437:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:450:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:454:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:464:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:467:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:476:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:480:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:491:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:495:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:506:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:513:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:521:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:536:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:540:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:553:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:557:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:570:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:574:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:588:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:592:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:605:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:609:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:618:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:622:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:634:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:641:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:646:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:657:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:661:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:671:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* recreate crypt because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:678:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:692:21: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OR_PRINT (crypt, status);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:695:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:721:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:728:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:732:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:744:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:752:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:756:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:769:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:806:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:813:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:814:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:815:45: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_setopt_schema_map (crypt, schema_map), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:815:65: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_setopt_schema_map (crypt, schema_map), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:816:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:816:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:819:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:835:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:851:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:860:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:868:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:874:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:880:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:901:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:909:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:917:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:921:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:929:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:942:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:949:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:953:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:975:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:991:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1011:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1018:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1022:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1034:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1041:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1051:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1062:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1067:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1068:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1070:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt, TEST_FILE ("./test/data/schema-map.json")),
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1071:15: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1072:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1072:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1073:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1086:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1092:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1096:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1102:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1109:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1114:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1128:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1135:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1141:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1150:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1218:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1222:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1242:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1249:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1253:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1268:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1277:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1284:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1306:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1312:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1320:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1340:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1363:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1370:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1374:51: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_setopt_kms_provider_aws (crypt, "", -1, "", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1375:15: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1376:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1376:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1378:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1389:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1395:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1403:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:1424:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:96:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:105:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:143:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:150:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:170:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:177:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:203:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:210:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:245:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:252:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:284:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:292:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:356:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:363:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:408:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:415:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:507:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:514:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:556:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:563:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:600:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:607:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:624:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:632:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-setopt.c:664:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:36:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:69:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:78:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:92:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:179:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:185:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:195:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:226:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:111:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:125:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:163:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:200:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:209:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:246:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:282:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:320:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:327:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:343:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:357:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:369:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:381:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:390:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:405:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:438:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:453:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:459:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:474:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:494:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* destroy crypt to reset cache. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:498:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:515:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* destroy crypt to reset cache. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:519:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:547:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:554:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:564:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:574:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:581:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:592:46: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
_mongocrypt_key_broker_init (&key_broker, crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-broker.c:617:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-cache.c:444:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-cache.c:454:33: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-cache.c:464:27: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-kms-responses.c:37:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-kms-responses.c:60:36: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-kms-responses.c:65:36: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-kms-responses.c:115:27: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-local-kms.c:22:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-local-kms.c:31:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-local-kms.c:54:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt); /* destroy because of caching. */
data/libmongocrypt-1.0.4/test/test-mongocrypt-local-kms.c:58:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-local-kms.c:82:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:49:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:63:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:70:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:92:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt, expected_string, 5, expected_string, expected_int);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:96:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:104:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:118:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:119:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:119:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:123:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:398:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:410:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:419:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:445:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:450:35: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_log_handler (crypt, _mongocrypt_stdout_log_fn, NULL);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:451:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:454:42: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_local (crypt, localkey);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:456:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:456:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:457:11: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
return crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:464:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:471:35: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_init (crypt), crypt, "no kms provider set");
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:471:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_init (crypt), crypt, "no kms provider set");
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:472:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:477:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, NULL, -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:478:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:480:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:484:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, NULL, -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:485:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:487:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:494:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, &tmp, 1),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:495:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:497:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:500:56: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_setopt_kms_provider_local (crypt, NULL),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:501:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:503:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:507:56: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_setopt_kms_provider_local (crypt, local_key),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:508:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:511:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:516:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:517:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:518:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:518:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:519:35: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_init (crypt), crypt, "already initialized");
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:519:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_init (crypt), crypt, "already initialized");
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:520:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:524:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:525:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:526:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:526:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:528:43: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_kms_provider_aws (crypt, "example", -1, "example", -1),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:529:7: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:531:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:554:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:559:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt, TEST_FILE ("./test/data/schema-map.json")),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:560:15: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:562:21: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt, TEST_FILE ("./test/data/schema-map.json")),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:563:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:567:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:570:37: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_schema_map (crypt, NULL), crypt, "passed null schema");
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:570:51: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_setopt_schema_map (crypt, NULL), crypt, "passed null schema");
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:572:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:574:48: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_setopt_schema_map (crypt, TEST_BIN (0)),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:575:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:579:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:581:48: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_FAILS (mongocrypt_setopt_schema_map (crypt, TEST_BIN (10)),
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:582:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
crypt,
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:584:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:590:18: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_t *crypt;
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:595:51: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_setopt_kms_provider_aws (crypt, "", 0, "", 0), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:595:73: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_setopt_kms_provider_aws (crypt, "", 0, "", 0), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:596:32: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:596:40: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ASSERT_OK (mongocrypt_init (crypt), crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:598:30: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
ctx = mongocrypt_ctx_new (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:610:24: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
mongocrypt_destroy (crypt);
data/libmongocrypt-1.0.4/test/test-mongocrypt.h:95:10: [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, \
data/libmongocrypt-1.0.4/test/test-mongocrypt.h:119:10: [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, \
data/libmongocrypt-1.0.4/test/test-mongocrypt.h:134:10: [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, \
data/libmongocrypt-1.0.4/test/test-mongocrypt.h:139:10: [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, \
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:366:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
random,
data/libmongocrypt-1.0.4/src/mongocrypt-crypto-private.h:36:25: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
mongocrypt_random_fn random;
data/libmongocrypt-1.0.4/src/mongocrypt-crypto.c:160:22: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
return crypto->random (crypto->ctx, &out_bin, count, status);
data/libmongocrypt-1.0.4/src/mongocrypt-log.c:30:26: [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.
log->trace_enabled = (getenv ("MONGOCRYPT_TRACE") != NULL);
data/libmongocrypt-1.0.4/src/mongocrypt.c:460:54: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
mongocrypt_random_fn random,
data/libmongocrypt-1.0.4/src/mongocrypt.c:502:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
if (!random) {
data/libmongocrypt-1.0.4/src/mongocrypt.c:506:28: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
crypt->crypto->random = random;
data/libmongocrypt-1.0.4/src/os_win/os_mutex.c:24:4: [3] (misc) InitializeCriticalSection:
Exceptions can be thrown in low-memory situations. Use
InitializeCriticalSectionAndSpinCount instead.
InitializeCriticalSection (mutex);
data/libmongocrypt-1.0.4/src/os_win/os_mutex.c:36:4: [3] (misc) EnterCriticalSection:
On some versions of Windows, exceptions can be thrown in low-memory
situations. Use InitializeCriticalSectionAndSpinCount instead.
EnterCriticalSection (mutex);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:468:25: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
_mongocrypt_buffer_t random;
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:476:30: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
_mongocrypt_buffer_init (&random);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:477:32: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
_mongocrypt_buffer_resize (&random, 96);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:481:46: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ret = _mongocrypt_random (crypt->crypto, &random, random.len, status);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:481:54: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ret = _mongocrypt_random (crypt->crypto, &random, random.len, status);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:490:54: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
BSON_ASSERT (0 == _mongocrypt_buffer_cmp_hex (&random, RANDOM_HEX));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:495:33: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
_mongocrypt_buffer_cleanup (&random);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:84:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:93:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:102:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:111:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:146:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:163:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:180:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:197:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:214:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:231:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:257:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:276:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:295:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:314:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:333:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ctx-encrypt.c:351:53: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ASSERT_OK (mongocrypt_ctx_setopt_algorithm (ctx, random, -1), ctx);
data/libmongocrypt-1.0.4/bindings/node/src/mongocrypt.cc:42: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(buffer_copy, buffer, buffer_len);
data/libmongocrypt-1.0.4/kms-message/src/hexlify.c:33:12: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
p += sprintf (p, "%02x", buf[i]);
data/libmongocrypt-1.0.4/kms-message/src/kms_message_private.h:28:4: [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 error[512];
data/libmongocrypt-1.0.4/kms-message/src/kms_message_private.h:62:4: [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 error[512];
data/libmongocrypt-1.0.4/kms-message/src/kms_port.c:28:4: [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, len);
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:107:7: [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 (&request->crypto, &opt->crypto, sizeof (opt->crypto));
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:145:4: [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[sizeof AMZ_DT_FORMAT];
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:575:13: [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.
unsigned char k_date[32];
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:576:13: [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.
unsigned char k_region[32];
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:577:13: [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.
unsigned char k_service[32];
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:623:13: [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.
unsigned char signing_key[32];
data/libmongocrypt-1.0.4/kms-message/src/kms_request.c:624:13: [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.
unsigned char signature[32];
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:79:4: [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 (s->str, chars, actual_len);
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:177:4: [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 (str->str, chars, actual_len + 1);
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:199:4: [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 (str->str + str->len, appended->str, appended->len);
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:223:4: [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 (str->str + str->len, appended, (size_t) len);
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:307:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf ((char *) out, "%%%02X", *in);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:120:4: [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 file_path[PATH_MAX];
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:200:8: [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).
f = fopen (file_path, "r");
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:267:8: [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).
f = fopen (file_path, "r");
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:441:4: [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 sub[PATH_MAX];
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:493:13: [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.
unsigned char signing[32];
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:765:4: [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 encoded[9];
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:786:20: [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).
response_file = fopen ("./test/example-response.bin", "rb");
data/libmongocrypt-1.0.4/kms-message/test/windows/dirent.h:230:5: [2] (buffer) wchar_t:
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.
wchar_t d_name[PATH_MAX+1];
data/libmongocrypt-1.0.4/kms-message/test/windows/dirent.h:270: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 d_name[PATH_MAX+1];
data/libmongocrypt-1.0.4/kms-message/test/windows/dirent.h:680:9: [2] (buffer) wchar_t:
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.
wchar_t wname[PATH_MAX + 1];
data/libmongocrypt-1.0.4/kms-message/test/windows/dirent.h:1095:9: [2] (buffer) MultiByteToWideChar:
Requires maximum length in CHARACTERS, not bytes (CWE-120).
n = MultiByteToWideChar(
data/libmongocrypt-1.0.4/src/crypto/cng.c:134:4: [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 (keyBlob, &blobHeader, sizeof (BCRYPT_KEY_DATA_BLOB_HEADER));
data/libmongocrypt-1.0.4/src/crypto/cng.c:136:4: [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 (keyBlob + sizeof (BCRYPT_KEY_DATA_BLOB_HEADER), key->data, key->len);
data/libmongocrypt-1.0.4/src/crypto/cng.c:158:4: [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 (state->iv, iv->data, iv->len);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:40:4: [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 (buf->data, tmp, buf->len);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:235:4: [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, src->data, src->len);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:309:4: [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_prefix, plaintext->data, plaintext->len);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:310:4: [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, &le_data_len, INT32_LEN);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:311:4: [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 + INT32_LEN, &type, TYPE_LEN);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:365:4: [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 (plaintext->data, wrapper_data + offset, plaintext->len);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:452:7: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (out, "%02X", buf->data[i]);
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:479:7: [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 + offset, srcs[i].data, srcs[i].len);
data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext.c:139:4: [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 + offset, ciphertext->key_id.data, ciphertext->key_id.len);
data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext.c:145:4: [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 + offset, ciphertext->data.data, ciphertext->data.len);
data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext.c:187:4: [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, &ciphertext->blob_subtype, 1);
data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext.c:189:4: [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 + bytes_written,
data/libmongocrypt-1.0.4/src/mongocrypt-ciphertext.c:193:4: [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 + bytes_written, &ciphertext->original_bson_type, 1);
data/libmongocrypt-1.0.4/src/mongocrypt-crypto.c:315:7: [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 (intermediates[1].data,
data/libmongocrypt-1.0.4/src/mongocrypt-crypto.c:448:4: [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, tag.data, MONGOCRYPT_HMAC_LEN);
data/libmongocrypt-1.0.4/src/mongocrypt-crypto.c:537:4: [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 (intermediate.data, iv->data, iv->len);
data/libmongocrypt-1.0.4/src/mongocrypt-crypto.c:908:4: [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, tag.data, MONGOCRYPT_IV_LEN);
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c:384:7: [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 (&marking.v_iter, &iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c:675:7: [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 (&ns_iter, &iter, sizeof (iter));
data/libmongocrypt-1.0.4/src/mongocrypt-marking.c:90:10: [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->v_iter, &iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/src/mongocrypt-status.c:59:4: [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 (status->message, message, message_len - 1);
data/libmongocrypt-1.0.4/src/mongocrypt-traverse-util.c:97:10: [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 (&child_state, state, sizeof (_recurse_state_t));
data/libmongocrypt-1.0.4/src/mongocrypt-traverse-util.c:125:10: [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 (&child_state, state, sizeof (_recurse_state_t));
data/libmongocrypt-1.0.4/src/mongocrypt.c:72:11: [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 storage[1024];
data/libmongocrypt-1.0.4/src/mongocrypt.c:86:11: [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 storage[1024];
data/libmongocrypt-1.0.4/src/mongocrypt.c:224:7: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (out, "%02X", src[i]);
data/libmongocrypt-1.0.4/test/example-state-machine.c:63:4: [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 storage[512];
data/libmongocrypt-1.0.4/test/example-state-machine.c:67:9: [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 (path, O_RDONLY);
data/libmongocrypt-1.0.4/test/example-state-machine.c:71:7: [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 (contents + (filesize - n_read), storage, n_read);
data/libmongocrypt-1.0.4/test/test-mongocrypt-buffer.c:31:7: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (dest, "%02X ", src[i]);
data/libmongocrypt-1.0.4/test/test-mongocrypt-buffer.c:44:4: [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 actual[100] = {0};
data/libmongocrypt-1.0.4/test/test-mongocrypt-buffer.c:52:4: [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 (&marking.v_iter, &iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:154:4: [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 (&marking.v_iter, &a_iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:161:4: [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 (&marking.v_iter, &a_iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:168:4: [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 (&marking.v_iter, &a_iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:175:4: [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 (&marking.v_iter, &b_iter, sizeof (bson_iter_t));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:78:4: [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 + *bytes_written, in->data, in->len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:104:4: [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 + *bytes_written, in->data, in->len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:132:4: [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, tmp.data, tmp.len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:159:4: [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, tmp.data, tmp.len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:184:4: [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, tmp.data, tmp.len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:210:4: [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, tmp.data, count);
data/libmongocrypt-1.0.4/test/test-mongocrypt-datakey.c:41:4: [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 zero[TEST_COUNT];
data/libmongocrypt-1.0.4/test/test-mongocrypt-key-cache.c:168:4: [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/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:106:4: [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 captured_logs[buffer_size];
data/libmongocrypt-1.0.4/test/test-mongocrypt-marking.c:34:4: [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 (buf->data + 1, bson_get_data (bson), bson->len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:38:4: [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 + 1, marking_bson, marking_bson->len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:66:4: [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 + 1, (TEST_BIN (16))->data, key_id_len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:68:4: [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 + key_id_len + 2, utf8, strlen (utf8));
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:116:4: [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 name[36];
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:174:4: [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 name[24];
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:397:4: [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.v_binary.data + 1, "secretmessage", 13);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:87:4: [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 storage[512];
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:93:9: [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 (path, O_RDONLY);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:98:7: [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 (contents + (filesize - n_read), storage, n_read);
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:446:4: [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 localkey_data[MONGOCRYPT_KEY_LEN] = {0};
data/libmongocrypt-1.0.4/test/test-mongocrypt.h:38:4: [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 *test_names[TEST_DATA_COUNT];
data/libmongocrypt-1.0.4/test/test-mongocrypt.h:42:4: [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 *file_paths[TEST_DATA_COUNT];
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:74:27: [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).
actual_len = len < 0 ? strlen (chars) : (size_t) len;
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:100:23: [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).
s->len = len < 0 ? strlen (chars) : (size_t) len;
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:175:34: [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 actual_len = len < 0 ? strlen (chars) : (size_t) len;
data/libmongocrypt-1.0.4/kms-message/src/kms_request_str.c:220:13: [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 (appended);
data/libmongocrypt-1.0.4/kms-message/src/kms_response_parser.c:97:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (num_str, str + start, end - start);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:90: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 str_len = strlen (str);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:91: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 suf_len = strlen (suffix);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:104:26: [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 = str + strlen (str);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:157:15: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int c = fgetc (stream);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:277:27: [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).
kms_strndup (line + strlen (method) + 1,
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:278: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).
line_len - strlen (method) - 1 - strlen (" HTTP/1.1\n"));
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:278:53: [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).
line_len - strlen (method) - 1 - strlen (" HTTP/1.1\n"));
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:329: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).
size_t len = strlen (x) > strlen (y) ? strlen (x) : strlen (y);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:329: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).
size_t len = strlen (x) > strlen (y) ? strlen (x) : strlen (y);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:329: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).
size_t len = strlen (x) > strlen (y) ? strlen (x) : strlen (y);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:329:56: [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 (x) > strlen (y) ? strlen (x) : strlen (y);
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:338:8: [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 (strlen (x) > strlen (y)) {
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:338: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).
if (strlen (x) > strlen (y)) {
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:339:14: [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 strlen (y) + 1;
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:342:8: [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 (strlen (y) > strlen (x)) {
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:342: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).
if (strlen (y) > strlen (x)) {
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:343:14: [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 strlen (x) + 1;
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:360: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).
strlen (expect),
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:362: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).
strlen (actual),
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:593:50: [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).
kms_request_append_payload (request, payload, strlen (payload));
data/libmongocrypt-1.0.4/kms-message/test/test_kms_request.c:719: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).
(uint8_t *) plaintext, strlen (plaintext), "alias/1", NULL);
data/libmongocrypt-1.0.4/kms-message/test/windows/dirent.h:372:17: [1] (buffer) wcslen:
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).
n = wcslen(dirname);
data/libmongocrypt-1.0.4/src/crypto/cng.c:61:35: [1] (buffer) wcslen:
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).
(ULONG) (sizeof (wchar_t) * wcslen (BCRYPT_CHAIN_MODE_CBC)),
data/libmongocrypt-1.0.4/src/mongocrypt-buffer.c:419:26: [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).
buf->len = (uint32_t) strlen (hex) / 2;
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c:769: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 (0 == strlen (*collname)) {
data/libmongocrypt-1.0.4/src/mongocrypt-ctx-encrypt.c:845:13: [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).
0 == strlen (ectx->db_name)) {
data/libmongocrypt-1.0.4/src/mongocrypt-ctx.c:206:33: [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).
calculated_len = len == -1 ? strlen (algorithm) : (size_t) len;
data/libmongocrypt-1.0.4/src/mongocrypt-key-broker.c:350:53: [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).
&req->id, &ids, key_str, (uint32_t) strlen (key_str))) {
data/libmongocrypt-1.0.4/src/mongocrypt-key-broker.c:369:45: [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).
(uint32_t) strlen (key_str),
data/libmongocrypt-1.0.4/src/mongocrypt-key.c:484:49: [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).
curr->value.value.v_utf8.len = (uint32_t) strlen (arg_ptr);
data/libmongocrypt-1.0.4/src/mongocrypt-kms-ctx.c:200: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).
kms->msg.len = (uint32_t) strlen ((char *) kms->msg.data);
data/libmongocrypt-1.0.4/src/mongocrypt-kms-ctx.c:316: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).
kms->msg.len = (uint32_t) strlen ((char *) kms->msg.data);
data/libmongocrypt-1.0.4/src/mongocrypt-log.c:104: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).
log->fn (level, message, (uint32_t) strlen (message), log->ctx);
data/libmongocrypt-1.0.4/src/mongocrypt-status.c:48: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).
message_len = (int32_t) strlen (message) + 1;
data/libmongocrypt-1.0.4/src/mongocrypt.c:39:25: [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 = (uint32_t) strlen (MONGOCRYPT_VERSION);
data/libmongocrypt-1.0.4/src/mongocrypt.c:445:27: [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).
in_len = (uint32_t) strlen (in);
data/libmongocrypt-1.0.4/test/example-state-machine.c:68:21: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((n_read = read (fd, storage, sizeof (storage))) > 0) {
data/libmongocrypt-1.0.4/test/test-mongocrypt-cache.c:95:4: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep ((useconds_t) usec);
data/libmongocrypt-1.0.4/test/test-mongocrypt-ciphertext.c:245:57: [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).
BSON_ASSERT (0 == memcmp (serialized.data, expected, strlen (expected)));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:72:58: [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).
BSON_ASSERT (0 == strncmp ("error_on:", (char *) ctx, strlen ("error_on:")));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:98:58: [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).
BSON_ASSERT (0 == strncmp ("error_on:", (char *) ctx, strlen ("error_on:")));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:124:58: [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).
BSON_ASSERT (0 == strncmp ("error_on:", (char *) ctx, strlen ("error_on:")));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:151:58: [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).
BSON_ASSERT (0 == strncmp ("error_on:", (char *) ctx, strlen ("error_on:")));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:177:58: [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).
BSON_ASSERT (0 == strncmp ("error_on:", (char *) ctx, strlen ("error_on:")));
data/libmongocrypt-1.0.4/test/test-mongocrypt-crypto-hooks.c:203:58: [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).
BSON_ASSERT (0 == strncmp ("error_on:", (char *) ctx, strlen ("error_on:")));
data/libmongocrypt-1.0.4/test/test-mongocrypt-log.c:124: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).
BSON_ASSERT (strlen(captured_logs) == 0);
data/libmongocrypt-1.0.4/test/test-mongocrypt-status.c:50: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).
BSON_ASSERT (strlen (somestring) == out_len);
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:60: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).
data_len = (int) (1 + key_id_len + 1 + strlen (utf8));
data/libmongocrypt-1.0.4/test/test-mongocrypt-traverse-util.c:68:41: [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).
memcpy (data + key_id_len + 2, utf8, strlen (utf8));
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:94:21: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((n_read = read (fd, storage, sizeof (storage))) > 0) {
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:211: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).
if (!bson_init_from_json (bson, full_json, strlen (full_json), &error)) {
data/libmongocrypt-1.0.4/test/test-mongocrypt.c:243: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).
if (!bson_init_from_json (bson, full_json, strlen (full_json), &error)) {
ANALYSIS SUMMARY:
Hits = 607
Lines analyzed = 25830 in approximately 1.18 seconds (21965 lines/second)
Physical Source Lines of Code (SLOC) = 18273
Hits@level = [0] 85 [1] 57 [2] 89 [3] 32 [4] 429 [5] 0
Hits@level+ = [0+] 692 [1+] 607 [2+] 550 [3+] 461 [4+] 429 [5+] 0
Hits/KSLOC@level+ = [0+] 37.8701 [1+] 33.2184 [2+] 30.0991 [3+] 25.2285 [4+] 23.4773 [5+] 0
Dot directories skipped = 5 (--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.