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/reaver-1.6.5/src/pixie.h
Examining data/reaver-1.6.5/src/sigalrm.c
Examining data/reaver-1.6.5/src/sigint.h
Examining data/reaver-1.6.5/src/wps.h
Examining data/reaver-1.6.5/src/sigint.c
Examining data/reaver-1.6.5/src/defs.h
Examining data/reaver-1.6.5/src/crc.h
Examining data/reaver-1.6.5/src/misc.c
Examining data/reaver-1.6.5/src/wps/wps.h
Examining data/reaver-1.6.5/src/wps/wps_attr_parse.c
Examining data/reaver-1.6.5/src/wps/wps_registrar.c
Examining data/reaver-1.6.5/src/wps/wps_ufd.c
Examining data/reaver-1.6.5/src/wps/wps_attr_process.c
Examining data/reaver-1.6.5/src/wps/wps_dev_attr.c
Examining data/reaver-1.6.5/src/wps/wps_attr_build.c
Examining data/reaver-1.6.5/src/wps/wps_dev_attr.h
Examining data/reaver-1.6.5/src/wps/wps_common.c
Examining data/reaver-1.6.5/src/wps/wps_enrollee.c
Examining data/reaver-1.6.5/src/wps/wps_i.h
Examining data/reaver-1.6.5/src/wps/wps.c
Examining data/reaver-1.6.5/src/wps/wps_defs.h
Examining data/reaver-1.6.5/src/builder.h
Examining data/reaver-1.6.5/src/wpscrack.c
Examining data/reaver-1.6.5/src/wpsmon.h
Examining data/reaver-1.6.5/src/80211.h
Examining data/reaver-1.6.5/src/main.c
Examining data/reaver-1.6.5/src/libwps/libwps.h
Examining data/reaver-1.6.5/src/libwps/libwps.c
Examining data/reaver-1.6.5/src/send.h
Examining data/reaver-1.6.5/src/send.c
Examining data/reaver-1.6.5/src/cracker.h
Examining data/reaver-1.6.5/src/lwe/iwlib.c
Examining data/reaver-1.6.5/src/lwe/iwlib.h
Examining data/reaver-1.6.5/src/lwe/wireless.21.h
Examining data/reaver-1.6.5/src/builder.c
Examining data/reaver-1.6.5/src/pins.c
Examining data/reaver-1.6.5/src/cprintf.h
Examining data/reaver-1.6.5/src/pins.h
Examining data/reaver-1.6.5/src/session.c
Examining data/reaver-1.6.5/src/iface.h
Examining data/reaver-1.6.5/src/pixie.c
Examining data/reaver-1.6.5/src/globule.h
Examining data/reaver-1.6.5/src/sigalrm.h
Examining data/reaver-1.6.5/src/session.h
Examining data/reaver-1.6.5/src/argsparser.c
Examining data/reaver-1.6.5/src/init.h
Examining data/reaver-1.6.5/src/crypto/sha1.c
Examining data/reaver-1.6.5/src/crypto/des-internal.c
Examining data/reaver-1.6.5/src/crypto/des_i.h
Examining data/reaver-1.6.5/src/crypto/crypto_gnutls.c
Examining data/reaver-1.6.5/src/crypto/crypto_internal.c
Examining data/reaver-1.6.5/src/crypto/aes-internal-enc.c
Examining data/reaver-1.6.5/src/crypto/aes-omac1.c
Examining data/reaver-1.6.5/src/crypto/aes_i.h
Examining data/reaver-1.6.5/src/crypto/aes-encblock.c
Examining data/reaver-1.6.5/src/crypto/tls_nss.c
Examining data/reaver-1.6.5/src/crypto/md5.c
Examining data/reaver-1.6.5/src/crypto/aes.h
Examining data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c
Examining data/reaver-1.6.5/src/crypto/crypto_nss.c
Examining data/reaver-1.6.5/src/crypto/rc4.c
Examining data/reaver-1.6.5/src/crypto/tls_internal.c
Examining data/reaver-1.6.5/src/crypto/sha1-tlsprf.c
Examining data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c
Examining data/reaver-1.6.5/src/crypto/sha256.c
Examining data/reaver-1.6.5/src/crypto/aes-internal.c
Examining data/reaver-1.6.5/src/crypto/dh_group5.h
Examining data/reaver-1.6.5/src/crypto/ms_funcs.c
Examining data/reaver-1.6.5/src/crypto/aes_wrap.h
Examining data/reaver-1.6.5/src/crypto/sha1-tprf.c
Examining data/reaver-1.6.5/src/crypto/milenage.c
Examining data/reaver-1.6.5/src/crypto/md5-non-fips.c
Examining data/reaver-1.6.5/src/crypto/crypto_openssl.c
Examining data/reaver-1.6.5/src/crypto/tls_schannel.c
Examining data/reaver-1.6.5/src/crypto/crypto.h
Examining data/reaver-1.6.5/src/crypto/crypto_internal-rsa.c
Examining data/reaver-1.6.5/src/crypto/fips_prf_nss.c
Examining data/reaver-1.6.5/src/crypto/md5_i.h
Examining data/reaver-1.6.5/src/crypto/fips_prf_openssl.c
Examining data/reaver-1.6.5/src/crypto/sha256.h
Examining data/reaver-1.6.5/src/crypto/aes-ctr.c
Examining data/reaver-1.6.5/src/crypto/md5.h
Examining data/reaver-1.6.5/src/crypto/fips_prf_internal.c
Examining data/reaver-1.6.5/src/crypto/tls_openssl.c
Examining data/reaver-1.6.5/src/crypto/sha1_i.h
Examining data/reaver-1.6.5/src/crypto/sha256-internal.c
Examining data/reaver-1.6.5/src/crypto/aes-unwrap.c
Examining data/reaver-1.6.5/src/crypto/milenage.h
Examining data/reaver-1.6.5/src/crypto/dh_groups.c
Examining data/reaver-1.6.5/src/crypto/tls.h
Examining data/reaver-1.6.5/src/crypto/sha1-internal.c
Examining data/reaver-1.6.5/src/crypto/crypto_none.c
Examining data/reaver-1.6.5/src/crypto/crypto_internal-modexp.c
Examining data/reaver-1.6.5/src/crypto/fips_prf_gnutls.c
Examining data/reaver-1.6.5/src/crypto/dh_group5.c
Examining data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c
Examining data/reaver-1.6.5/src/crypto/aes-eax.c
Examining data/reaver-1.6.5/src/crypto/tls_gnutls.c
Examining data/reaver-1.6.5/src/crypto/sha1-pbkdf2.c
Examining data/reaver-1.6.5/src/crypto/md5-internal.c
Examining data/reaver-1.6.5/src/crypto/fips_prf_cryptoapi.c
Examining data/reaver-1.6.5/src/crypto/aes-cbc.c
Examining data/reaver-1.6.5/src/crypto/aes-internal-dec.c
Examining data/reaver-1.6.5/src/crypto/ms_funcs.h
Examining data/reaver-1.6.5/src/crypto/tls_none.c
Examining data/reaver-1.6.5/src/crypto/md4-internal.c
Examining data/reaver-1.6.5/src/crypto/sha1.h
Examining data/reaver-1.6.5/src/crypto/dh_groups.h
Examining data/reaver-1.6.5/src/crypto/aes-wrap.c
Examining data/reaver-1.6.5/src/init.c
Examining data/reaver-1.6.5/src/utils/os.h
Examining data/reaver-1.6.5/src/utils/base64.h
Examining data/reaver-1.6.5/src/utils/ip_addr.c
Examining data/reaver-1.6.5/src/utils/vendor.c
Examining data/reaver-1.6.5/src/utils/radiotap.h
Examining data/reaver-1.6.5/src/utils/build_config.h
Examining data/reaver-1.6.5/src/utils/vendor.h
Examining data/reaver-1.6.5/src/utils/ip_addr.h
Examining data/reaver-1.6.5/src/utils/common.h
Examining data/reaver-1.6.5/src/utils/state_machine.h
Examining data/reaver-1.6.5/src/utils/wpa_debug.h
Examining data/reaver-1.6.5/src/utils/file.h
Examining data/reaver-1.6.5/src/utils/radiotap_iter.h
Examining data/reaver-1.6.5/src/utils/base64.c
Examining data/reaver-1.6.5/src/utils/eloop.c
Examining data/reaver-1.6.5/src/utils/trace.c
Examining data/reaver-1.6.5/src/utils/eloop_none.c
Examining data/reaver-1.6.5/src/utils/os_win32.c
Examining data/reaver-1.6.5/src/utils/eloop.h
Examining data/reaver-1.6.5/src/utils/pcsc_funcs.h
Examining data/reaver-1.6.5/src/utils/wpabuf.h
Examining data/reaver-1.6.5/src/utils/common.c
Examining data/reaver-1.6.5/src/utils/endianness.h
Examining data/reaver-1.6.5/src/utils/wpa_debug.c
Examining data/reaver-1.6.5/src/utils/list.h
Examining data/reaver-1.6.5/src/utils/pcsc_funcs.c
Examining data/reaver-1.6.5/src/utils/uuid.h
Examining data/reaver-1.6.5/src/utils/file.c
Examining data/reaver-1.6.5/src/utils/includes.h
Examining data/reaver-1.6.5/src/utils/os_internal.c
Examining data/reaver-1.6.5/src/utils/wpabuf.c
Examining data/reaver-1.6.5/src/utils/trace.h
Examining data/reaver-1.6.5/src/utils/uuid.c
Examining data/reaver-1.6.5/src/utils/os_unix.c
Examining data/reaver-1.6.5/src/utils/radiotap.c
Examining data/reaver-1.6.5/src/utils/os_none.c
Examining data/reaver-1.6.5/src/utils/eloop_win.c
Examining data/reaver-1.6.5/src/tls/rsa.c
Examining data/reaver-1.6.5/src/tls/x509v3.c
Examining data/reaver-1.6.5/src/tls/tlsv1_cred.c
Examining data/reaver-1.6.5/src/tls/pkcs1.h
Examining data/reaver-1.6.5/src/tls/pkcs5.c
Examining data/reaver-1.6.5/src/tls/libtommath.c
Examining data/reaver-1.6.5/src/tls/bignum.h
Examining data/reaver-1.6.5/src/tls/pkcs5.h
Examining data/reaver-1.6.5/src/tls/bignum.c
Examining data/reaver-1.6.5/src/tls/tlsv1_cred.h
Examining data/reaver-1.6.5/src/tls/tlsv1_server_read.c
Examining data/reaver-1.6.5/src/tls/tlsv1_common.h
Examining data/reaver-1.6.5/src/tls/tlsv1_server_i.h
Examining data/reaver-1.6.5/src/tls/x509v3.h
Examining data/reaver-1.6.5/src/tls/tlsv1_client.c
Examining data/reaver-1.6.5/src/tls/tlsv1_client.h
Examining data/reaver-1.6.5/src/tls/tlsv1_record.c
Examining data/reaver-1.6.5/src/tls/tlsv1_client_read.c
Examining data/reaver-1.6.5/src/tls/pkcs8.c
Examining data/reaver-1.6.5/src/tls/tlsv1_client_write.c
Examining data/reaver-1.6.5/src/tls/tlsv1_server.h
Examining data/reaver-1.6.5/src/tls/tlsv1_server_write.c
Examining data/reaver-1.6.5/src/tls/tlsv1_server.c
Examining data/reaver-1.6.5/src/tls/pkcs1.c
Examining data/reaver-1.6.5/src/tls/asn1.c
Examining data/reaver-1.6.5/src/tls/tlsv1_record.h
Examining data/reaver-1.6.5/src/tls/asn1.h
Examining data/reaver-1.6.5/src/tls/pkcs8.h
Examining data/reaver-1.6.5/src/tls/tlsv1_common.c
Examining data/reaver-1.6.5/src/tls/tlsv1_client_i.h
Examining data/reaver-1.6.5/src/tls/rsa.h
Examining data/reaver-1.6.5/src/wpscrack.h
Examining data/reaver-1.6.5/src/common/defs.h
Examining data/reaver-1.6.5/src/common/wpa_ctrl.c
Examining data/reaver-1.6.5/src/common/wpa_common.h
Examining data/reaver-1.6.5/src/common/wpa_common.c
Examining data/reaver-1.6.5/src/common/ieee802_11_common.c
Examining data/reaver-1.6.5/src/common/eapol_common.h
Examining data/reaver-1.6.5/src/common/wpa_ctrl.h
Examining data/reaver-1.6.5/src/common/ieee802_11_common.h
Examining data/reaver-1.6.5/src/common/ieee802_11_defs.h
Examining data/reaver-1.6.5/src/common/privsep_commands.h
Examining data/reaver-1.6.5/src/argsparser.h
Examining data/reaver-1.6.5/src/80211.c
Examining data/reaver-1.6.5/src/iface.c
Examining data/reaver-1.6.5/src/wpsmon.c
Examining data/reaver-1.6.5/src/radiotap_flags.h
Examining data/reaver-1.6.5/src/exchange.h
Examining data/reaver-1.6.5/src/misc.h
Examining data/reaver-1.6.5/src/crc.c
Examining data/reaver-1.6.5/src/cracker.c
Examining data/reaver-1.6.5/src/version.c
Examining data/reaver-1.6.5/src/keys.c
Examining data/reaver-1.6.5/src/keys.h
Examining data/reaver-1.6.5/src/exchange.c
Examining data/reaver-1.6.5/src/globule.c
FINAL RESULTS:
data/reaver-1.6.5/src/utils/trace.c:42:8: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
len = readlink(exe, fname, sizeof(fname) - 1);
data/reaver-1.6.5/src/crypto/aes-internal-dec.c:141:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain)
data/reaver-1.6.5/src/crypto/aes-internal-dec.c:143: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.
rijndaelDecrypt(ctx, crypt, plain);
data/reaver-1.6.5/src/crypto/aes-internal-enc.c:111:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt)
data/reaver-1.6.5/src/crypto/aes-internal-enc.c:113: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.
rijndaelEncrypt(ctx, plain, crypt);
data/reaver-1.6.5/src/crypto/aes.h:21:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt);
data/reaver-1.6.5/src/crypto/aes.h:24:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain);
data/reaver-1.6.5/src/crypto/crypto.h:125:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt);
data/reaver-1.6.5/src/crypto/crypto.h:147:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain);
data/reaver-1.6.5/src/crypto/crypto.h:247: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.
const u8 *plain, u8 *crypt, size_t len);
data/reaver-1.6.5/src/crypto/crypto.h:262:22: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
const u8 *crypt, u8 *plain, size_t len);
data/reaver-1.6.5/src/crypto/crypto.h:407: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.
struct crypto_public_key *key, const u8 *crypt, size_t crypt_len,
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:297:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt)
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:302:12: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, plain, 16);
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:304: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.
if (!CryptEncrypt(akey->ckey, 0, FALSE, 0, crypt, &dlen, 16)) {
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:307:13: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memset(crypt, 0, 16);
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:329:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain)
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:334:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(plain, crypt, 16);
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:597:10: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
u8 *crypt, size_t len)
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:601:12: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, plain, len);
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:603: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.
if (!CryptEncrypt(ctx->key, 0, FALSE, 0, crypt, &dlen, len)) {
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:605:13: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memset(crypt, 0, len);
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:613: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.
int crypto_cipher_decrypt(struct crypto_cipher *ctx, const u8 *crypt,
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:618:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(plain, crypt, len);
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:116:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt)
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:119: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.
gcry_cipher_encrypt(hd, crypt, 16, plain, 16);
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:146:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain)
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:149: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.
gcry_cipher_decrypt(hd, plain, 16, crypt, 16);
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:281:10: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
u8 *crypt, size_t len)
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:283: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.
if (gcry_cipher_encrypt(ctx->enc, crypt, len, plain, len) !=
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:290: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.
int crypto_cipher_decrypt(struct crypto_cipher *ctx, const u8 *crypt,
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:293: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.
if (gcry_cipher_decrypt(ctx->dec, plain, len, crypt, len) !=
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:116:10: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
u8 *crypt, size_t len)
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:122: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.
if (plain != crypt)
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:123:14: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, plain, len);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:125:28: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to 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->u.rc4.used_bytes, crypt, len);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:137:14: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, ctx->u.aes.cbc,
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:152:14: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, ctx->u.des3.cbc, 8);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:166:14: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, ctx->u.des.cbc, 8);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:179: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.
int crypto_cipher_decrypt(struct crypto_cipher *ctx, const u8 *crypt,
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:187: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.
if (plain != crypt)
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:188: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.
os_memcpy(plain, crypt, len);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:198:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(tmp, crypt, ctx->u.aes.block_size);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:199: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.
aes_decrypt(ctx->u.aes.ctx_dec, crypt, plain);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:212:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(tmp, crypt, 8);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:213: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.
des3_decrypt(crypt, &ctx->u.des3.key, plain);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:226:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(tmp, crypt, 8);
data/reaver-1.6.5/src/crypto/crypto_internal-cipher.c:227:22: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
des_block_decrypt(crypt, ctx->u.des.dk, plain);
data/reaver-1.6.5/src/crypto/crypto_internal-rsa.c:110:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
const u8 *crypt, size_t crypt_len,
data/reaver-1.6.5/src/crypto/crypto_internal-rsa.c:114:6: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to 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, crypt_len, plain, plain_len);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:105:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt)
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:108:25: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
aes_ecb_encrypt(plain, crypt, skey);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:134:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain)
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:137: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.
aes_ecb_encrypt(plain, (u8 *) crypt, skey);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:357:10: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
u8 *crypt, size_t len)
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:362: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.
if (plain != crypt)
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:363:14: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
os_memcpy(crypt, plain, len);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:365:28: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to 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->u.rc4.used_bytes, crypt, len);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:370: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.
res = cbc_encrypt(plain, crypt, len, &ctx->u.cbc);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:380: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.
int crypto_cipher_decrypt(struct crypto_cipher *ctx, const u8 *crypt,
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:386: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.
if (plain != crypt)
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:387: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.
os_memcpy(plain, crypt, len);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:394: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.
res = cbc_decrypt(crypt, plain, len, &ctx->u.cbc);
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:618:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
const u8 *crypt, size_t crypt_len,
data/reaver-1.6.5/src/crypto/crypto_libtomcrypt.c:626: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.
res = rsa_exptmod(crypt, crypt_len, plain, &len, PK_PUBLIC,
data/reaver-1.6.5/src/crypto/crypto_nss.c:150:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt)
data/reaver-1.6.5/src/crypto/crypto_nss.c:166:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain)
data/reaver-1.6.5/src/crypto/crypto_nss.c:198:10: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
u8 *crypt, size_t len)
data/reaver-1.6.5/src/crypto/crypto_nss.c:204: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.
int crypto_cipher_decrypt(struct crypto_cipher *ctx, const u8 *crypt,
data/reaver-1.6.5/src/crypto/crypto_openssl.c:224:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_encrypt(void *ctx, const u8 *plain, u8 *crypt)
data/reaver-1.6.5/src/crypto/crypto_openssl.c:226: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.
AES_encrypt(plain, crypt, ctx);
data/reaver-1.6.5/src/crypto/crypto_openssl.c:250:39: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void aes_decrypt(void *ctx, const u8 *crypt, u8 *plain)
data/reaver-1.6.5/src/crypto/crypto_openssl.c:252:14: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
AES_decrypt(crypt, plain, ctx);
data/reaver-1.6.5/src/crypto/crypto_openssl.c:346:12: [4] (crypto) EVP_des_cbc:
DES only supports a 56-bit keysize, which is too small given today's
computers (CWE-327). Use a different patent-free encryption algorithm with
a larger keysize, such as 3DES or AES.
cipher = EVP_des_cbc();
data/reaver-1.6.5/src/crypto/crypto_openssl.c:385:10: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
u8 *crypt, size_t len)
data/reaver-1.6.5/src/crypto/crypto_openssl.c:388: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.
if (!EVP_EncryptUpdate(&ctx->enc, crypt, &outl, plain, len))
data/reaver-1.6.5/src/crypto/crypto_openssl.c:394: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.
int crypto_cipher_decrypt(struct crypto_cipher *ctx, const u8 *crypt,
data/reaver-1.6.5/src/crypto/crypto_openssl.c:399:50: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to 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 (!EVP_DecryptUpdate(&ctx->dec, plain, &outl, crypt, len))
data/reaver-1.6.5/src/crypto/des-internal.c:440:60: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void des_block_encrypt(const u8 *plain, const u32 *ek, u8 *crypt)
data/reaver-1.6.5/src/crypto/des-internal.c:446: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.
WPA_PUT_BE32(crypt, work[0]);
data/reaver-1.6.5/src/crypto/des-internal.c:451: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.
void des_block_decrypt(const u8 *crypt, const u32 *dk, u8 *plain)
data/reaver-1.6.5/src/crypto/des-internal.c:454:25: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
work[0] = WPA_GET_BE32(crypt);
data/reaver-1.6.5/src/crypto/des-internal.c:474:70: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void des3_encrypt(const u8 *plain, const struct des3_key_s *key, u8 *crypt)
data/reaver-1.6.5/src/crypto/des-internal.c:483: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.
WPA_PUT_BE32(crypt, work[0]);
data/reaver-1.6.5/src/crypto/des-internal.c:488:29: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void des3_decrypt(const u8 *crypt, const struct des3_key_s *key, u8 *plain)
data/reaver-1.6.5/src/crypto/des-internal.c:492:25: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
work[0] = WPA_GET_BE32(crypt);
data/reaver-1.6.5/src/crypto/des_i.h:24:60: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void des_block_encrypt(const u8 *plain, const u32 *ek, u8 *crypt);
data/reaver-1.6.5/src/crypto/des_i.h:25: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.
void des_block_decrypt(const u8 *crypt, const u32 *dk, u8 *plain);
data/reaver-1.6.5/src/crypto/des_i.h:28:70: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void des3_encrypt(const u8 *plain, const struct des3_key_s *key, u8 *crypt);
data/reaver-1.6.5/src/crypto/des_i.h:29:29: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
void des3_decrypt(const u8 *crypt, const struct des3_key_s *key, u8 *plain);
data/reaver-1.6.5/src/crypto/tls_openssl.c:729:18: [4] (crypto) EVP_rc2_40_cbc:
These keysizes are too small given today's computers (CWE-327). Use a
different patent-free encryption algorithm with a larger keysize, such as
3DES or AES.
EVP_add_cipher(EVP_rc2_40_cbc());
data/reaver-1.6.5/src/lwe/iwlib.c:2216:2: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(name, np->n_name);
data/reaver-1.6.5/src/lwe/iwlib.c:2226:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(name, hp->h_name);
data/reaver-1.6.5/src/misc.c:44:3: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(nyu, sizeof nyu, PAT PAT PAT PAT PAT PBT, PRT(0), PRT(1), PRT(2), PRT(3), PRT(4), mac[5]);
data/reaver-1.6.5/src/misc.c:46:3: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(nyu, sizeof nyu, PBT PBT PBT PBT PBT PBT, mac[0], mac[1], mac[2], mac[3], mac[4], mac[5]);
data/reaver-1.6.5/src/misc.c:82:3: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vfprintf(get_log_file(), fmt, arg);
data/reaver-1.6.5/src/pixie.c:29:8: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
exit(system(cmd));
data/reaver-1.6.5/src/session.c:70:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(file, get_session());
data/reaver-1.6.5/src/session.c:224:4: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(file_name, get_session());
data/reaver-1.6.5/src/tls/pkcs1.c:134:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
const u8 *crypt, size_t crypt_len,
data/reaver-1.6.5/src/tls/pkcs1.c:141:25: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to 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 (crypto_rsa_exptmod(crypt, crypt_len, plain, &len, key, 0) < 0)
data/reaver-1.6.5/src/tls/pkcs1.h:25:19: [4] (crypto) crypt:
The crypt functions use a poor one-way hashing algorithm; since they only
accept passwords of 8 characters or fewer and only a two-byte salt, they
are excessively vulnerable to dictionary attacks given today's faster
computing equipment (CWE-327). Use a different algorithm, such as SHA-256,
with a larger, non-repeating salt.
const u8 *crypt, size_t crypt_len,
data/reaver-1.6.5/src/utils/common.h:92:8: [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.
#undef vsnprintf
data/reaver-1.6.5/src/utils/common.h:93:9: [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.
#define vsnprintf _vsnprintf
data/reaver-1.6.5/src/utils/common.h:338:52: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define PRINTF_FORMAT(a,b) __attribute__ ((format (printf, (a), (b))))
data/reaver-1.6.5/src/utils/common.h:353:5: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int snprintf(char *str, size_t size, const char *format, ...);
data/reaver-1.6.5/src/utils/common.h:356:5: [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.
int vsnprintf(char *str, size_t size, const char *format, va_list ap);
data/reaver-1.6.5/src/utils/os.h:457:21: [4] (format) _snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define os_snprintf _snprintf
data/reaver-1.6.5/src/utils/os.h:459:21: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define os_snprintf snprintf
data/reaver-1.6.5/src/utils/os.h:502:8: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#undef snprintf
data/reaver-1.6.5/src/utils/os.h:503:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define snprintf OS_DO_NOT_USE_snprintf
data/reaver-1.6.5/src/utils/os.h:505:9: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
#define strcpy OS_DO_NOT_USE_strcpy
data/reaver-1.6.5/src/utils/os_internal.c:466:8: [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.
ret = vsnprintf(str, size, format, ap);
data/reaver-1.6.5/src/utils/wpa_debug.c:117:4: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vfprintf(out_file, fmt, ap);
data/reaver-1.6.5/src/utils/wpa_debug.c:121:3: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vprintf(fmt, ap);
data/reaver-1.6.5/src/utils/wpa_debug.c:340:8: [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.
len = vsnprintf(buf, buflen, fmt, ap);
data/reaver-1.6.5/src/utils/wpa_debug.c:366:8: [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.
len = vsnprintf(buf, buflen, fmt, ap);
data/reaver-1.6.5/src/utils/wpa_debug.c:398:8: [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.
len = vsnprintf(buf, buflen, fmt, ap);
data/reaver-1.6.5/src/utils/wpabuf.c:299:8: [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.
res = vsnprintf(tmp, buf->size - buf->used, fmt, ap);
data/reaver-1.6.5/src/wpscrack.c:124:8: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
r = system(get_exec_string());
data/reaver-1.6.5/src/wpsmon.c:441:7: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(sane_ssid,ssid);
data/reaver-1.6.5/src/argsparser.c:91:13: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while((c = getopt_long(argc, argv, short_options, long_options, &long_opt_index)) != -1)
data/reaver-1.6.5/src/crypto/crypto_cryptoapi.c:58:8: [3] (misc) LoadLibrary:
Ensure that the full path to the library is specified, or current directory
may be used (CWE-829, CWE-20). Use registry entry or GetWindowsDirectory to
find library path, if you aren't already.
dll = LoadLibrary("crypt32");
data/reaver-1.6.5/src/crypto/tls_nss.c:244:8: [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.
dir = getenv("SSL_DIR");
data/reaver-1.6.5/src/crypto/tls_schannel.c:58:22: [3] (misc) LoadLibrary:
Ensure that the full path to the library is specified, or current directory
may be used (CWE-829, CWE-20). Use registry entry or GetWindowsDirectory to
find library path, if you aren't already.
global->hsecurity = LoadLibrary(TEXT("Secur32.dll"));
data/reaver-1.6.5/src/utils/common.c:234:5: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
int getopt(int argc, char *const argv[], const char *optstring)
data/reaver-1.6.5/src/utils/common.h:360:5: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
int getopt(int argc, char *const argv[], const char *optstring);
data/reaver-1.6.5/src/utils/os_internal.c:119: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.
return random();
data/reaver-1.6.5/src/utils/os_unix.c:186: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.
return random();
data/reaver-1.6.5/src/utils/pcsc_funcs.c:172:8: [3] (misc) LoadLibrary:
Ensure that the full path to the library is specified, or current directory
may be used (CWE-829, CWE-20). Use registry entry or GetWindowsDirectory to
find library path, if you aren't already.
dll = LoadLibrary("winscard");
data/reaver-1.6.5/src/wpsmon.c:146:13: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while((c = getopt_long(argc, argv, short_options, long_options, &long_opt_index)) != -1)
data/reaver-1.6.5/src/80211.c:67:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(header, pkt_header, sizeof(*header));
data/reaver-1.6.5/src/80211.c:324: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.
unsigned char packet[sizeof radio_tap + sizeof dot11_frame + DEAUTH_REASON_CODE_SIZE];
data/reaver-1.6.5/src/80211.c:327:2: [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(packet, &radio_tap, radio_tap_len);
data/reaver-1.6.5/src/80211.c:329:2: [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(packet + offset, &dot11_frame, dot11_frame_len);
data/reaver-1.6.5/src/80211.c:331:2: [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(packet + offset, DEAUTH_REASON_CODE, DEAUTH_REASON_CODE_SIZE);
data/reaver-1.6.5/src/80211.c:350: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.
unsigned char packet[ sizeof (struct radio_tap_header)
data/reaver-1.6.5/src/80211.c:358:2: [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(packet + offset, &radio_tap, radio_tap_len);
data/reaver-1.6.5/src/80211.c:360:2: [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(packet + offset, &dot11_frame, dot11_frame_len);
data/reaver-1.6.5/src/80211.c:362:2: [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(packet + offset, &management_frame, management_frame_len);
data/reaver-1.6.5/src/80211.c:378: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.
unsigned char ssid_tag[sizeof (struct tagged_parameter) + IW_ESSID_MAX_SIZE];
data/reaver-1.6.5/src/80211.c:379: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.
unsigned char rates_tag[128];
data/reaver-1.6.5/src/80211.c:380: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.
unsigned char wps_tag[sizeof (struct tagged_parameter) + WPS_TAG_SIZE];
data/reaver-1.6.5/src/80211.c:381: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.
unsigned char ht_tag[128];
data/reaver-1.6.5/src/80211.c:398: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.
unsigned char packet[512];
data/reaver-1.6.5/src/80211.c:401:2: [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(packet, &radio_tap, radio_tap_len);
data/reaver-1.6.5/src/80211.c:403:2: [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(packet+offset, &dot11_frame, dot11_frame_len);
data/reaver-1.6.5/src/80211.c:405:2: [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(packet+offset, &management_frame, management_frame_len);
data/reaver-1.6.5/src/80211.c:407:2: [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(packet+offset, ssid_tag, ssid_tag_len);
data/reaver-1.6.5/src/80211.c:409:2: [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(packet+offset, rates_tag, rates_tag_len);
data/reaver-1.6.5/src/80211.c:412:2: [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(packet+offset, ht_tag, ht_tag_len);
data/reaver-1.6.5/src/80211.c:415:2: [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(packet+offset, wps_tag, wps_tag_len);
data/reaver-1.6.5/src/80211.c:518:6: [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(ssid, ie, ie_len);
data/reaver-1.6.5/src/80211.c:599:33: [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(tag_data, (data + offset + tag_size), tag->len);
data/reaver-1.6.5/src/80211.c:634: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(&flags, packet + offset, 4);
data/reaver-1.6.5/src/argsparser.c:50:2: [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 bssid[MAC_ADDR_LEN] = { 0 };
data/reaver-1.6.5/src/argsparser.c:51:2: [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 mac[MAC_ADDR_LEN] = { 0 };
data/reaver-1.6.5/src/argsparser.c:114:48: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_rx_timeout(atoi(optarg));
data/reaver-1.6.5/src/argsparser.c:130:43: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_delay(atoi(optarg));
data/reaver-1.6.5/src/argsparser.c:133:48: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_lock_delay(atoi(optarg));
data/reaver-1.6.5/src/argsparser.c:151:48: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_fail_delay(atoi(optarg));
data/reaver-1.6.5/src/argsparser.c:157:54: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_max_pin_attempts(atoi(optarg));
data/reaver-1.6.5/src/argsparser.c:232:43: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_recurring_delay_count(atoi(x));
data/reaver-1.6.5/src/argsparser.c:233:37: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_recurring_delay(atoi(y));
data/reaver-1.6.5/src/argsparser.c:252:9: [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 pin7[8] = { 0 };
data/reaver-1.6.5/src/argsparser.c:253:9: [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 pin8[9] = { 0 };
data/reaver-1.6.5/src/argsparser.c:254:9: [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((void *) &pin7, pin, sizeof(pin7)-1);
data/reaver-1.6.5/src/argsparser.c:255:58: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
snprintf(pin8, 9, "%s%d", pin7, wps_pin_checksum(atoi(pin7)));
data/reaver-1.6.5/src/argsparser.c:266:2: [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 p1[5] = { 0 };
data/reaver-1.6.5/src/argsparser.c:267:2: [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 p2[4] = { 0 };
data/reaver-1.6.5/src/argsparser.c:275: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((void *) &p1, pin, sizeof(p1)-1);
data/reaver-1.6.5/src/argsparser.c:281: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((void *) &p2, pin+sizeof(p1)-1, sizeof(p2)-1);
data/reaver-1.6.5/src/builder.c:39:2: [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(rt_header, "\0\0" "\x08\0" "\0\0\0\0", 8);
data/reaver-1.6.5/src/builder.c:43:88: [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.
size_t build_dot11_frame_header_m(struct dot11_frame_header *fh, uint16_t fc, unsigned char dstmac[6])
data/reaver-1.6.5/src/builder.c:53:2: [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(fh->addr1, dstmac, MAC_ADDR_LEN);
data/reaver-1.6.5/src/builder.c:54:2: [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(fh->addr2, get_mac(), MAC_ADDR_LEN);
data/reaver-1.6.5/src/builder.c:55:2: [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(fh->addr3, dstmac, MAC_ADDR_LEN);
data/reaver-1.6.5/src/builder.c:151:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) packet, &rt_header, rt_len);
data/reaver-1.6.5/src/builder.c:153:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) ((char *) packet+offset), &dot11_header, dot11_len);
data/reaver-1.6.5/src/builder.c:155:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) ((char *) packet+offset), (void *) &ssid_tag, sizeof(ssid_tag));
data/reaver-1.6.5/src/builder.c:157:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) ((char *) packet+offset), essid, ssid_tag.len);
data/reaver-1.6.5/src/builder.c:160:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(packet+offset, ALL_TAGS, sizeof(ALL_TAGS) -1);
data/reaver-1.6.5/src/builder.c:188:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) packet, &rt_header, rt_len);
data/reaver-1.6.5/src/builder.c:189:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) ((char *) packet+rt_len), &dot11_header, dot11_len);
data/reaver-1.6.5/src/builder.c:190:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((void *) ((char *) packet+rt_len+dot11_len), &llc_header, llc_len);
data/reaver-1.6.5/src/builder.c:280:18: [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((void *) packet, snap_packet, snap_len);
data/reaver-1.6.5/src/builder.c:281:18: [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((void *) ((char *) packet+snap_len), dot1x_header, dot1x_len);
data/reaver-1.6.5/src/builder.c:339: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((void *) buf, snap_packet, snap_len);
data/reaver-1.6.5/src/builder.c:341: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((void *) ((char *) buf+offset), dot1x_header, dot1x_len);
data/reaver-1.6.5/src/builder.c:343: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((void *) ((char *) buf+offset), eap_header, eap_len);
data/reaver-1.6.5/src/builder.c:348: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((void *) ((char *) buf+offset), wfa_header, wfa_len);
data/reaver-1.6.5/src/builder.c:354: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((void *) ((char *) buf+offset), payload, payload_len);
data/reaver-1.6.5/src/builder.c:388: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((void *) buf, snap_packet, snap_len);
data/reaver-1.6.5/src/builder.c:390: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((void *) ((char *) buf+offset), dot1x_header, dot1x_len);
data/reaver-1.6.5/src/builder.c:392: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((void *) ((char *) buf+offset), eap_header, eap_len);
data/reaver-1.6.5/src/builder.c:413:45: [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.
size_t build_ssid_tagged_parameter(unsigned char buf[IW_ESSID_MAX_SIZE+2], char *essid)
data/reaver-1.6.5/src/builder.c:421:2: [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, &ssid_param, sizeof ssid_param);
data/reaver-1.6.5/src/builder.c:422:2: [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+2, essid, ssid_len);
data/reaver-1.6.5/src/builder.c:427:44: [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.
size_t build_wps_tagged_parameter(unsigned char buf[2+WPS_TAG_SIZE])
data/reaver-1.6.5/src/builder.c:436:2: [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, &wps_param, sizeof wps_param);
data/reaver-1.6.5/src/builder.c:437:2: [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+2, WPS_REGISTRAR_TAG, WPS_TAG_SIZE);
data/reaver-1.6.5/src/builder.c:454:2: [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, &supported_rates, srates_len);
data/reaver-1.6.5/src/builder.c:457:2: [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+offset, srates, srates_tag_size);
data/reaver-1.6.5/src/builder.c:469:2: [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+offset, &extended_rates, erates_len);
data/reaver-1.6.5/src/builder.c:471:2: [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+offset, erates, erates_tag_size);
data/reaver-1.6.5/src/builder.c:487:2: [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, &tag_htcaps, taglen);
data/reaver-1.6.5/src/builder.c:488:2: [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 + taglen, htcaps, htlen);
data/reaver-1.6.5/src/builder.h:73:45: [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.
size_t build_ssid_tagged_parameter(unsigned char buf[IW_ESSID_MAX_SIZE+2], char *essid);
data/reaver-1.6.5/src/builder.h:75:44: [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.
size_t build_wps_tagged_parameter(unsigned char buf[2+WPS_TAG_SIZE]);
data/reaver-1.6.5/src/common/wpa_common.c:591: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.
unsigned char hash[SHA256_MAC_LEN];
data/reaver-1.6.5/src/common/wpa_ctrl.c:143:2: [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[128];
data/reaver-1.6.5/src/common/wpa_ctrl.c:274:2: [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[10];
data/reaver-1.6.5/src/common/wpa_ctrl.c:346:2: [2] (buffer) TCHAR:
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.
TCHAR name[256];
data/reaver-1.6.5/src/cracker.c:300:9: [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 time_s[256] = { 0 };
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:33:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(mac, p, gcry_md_get_algo_dlen(GCRY_MD_MD4));
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:73:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(mac, p, gcry_md_get_algo_dlen(GCRY_MD_MD5));
data/reaver-1.6.5/src/crypto/crypto_gnutls.c:91:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(mac, p, gcry_md_get_algo_dlen(GCRY_MD_SHA1));
data/reaver-1.6.5/src/crypto/crypto_openssl.c:151: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.
unsigned char skip_buf[16];
data/reaver-1.6.5/src/crypto/md4-internal.c:32:31: [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 void MD4Final(unsigned char digest[MD4_DIGEST_LENGTH], MD4_CTX *ctx);
data/reaver-1.6.5/src/crypto/md4-internal.c:171:31: [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 void MD4Final(unsigned char digest[MD4_DIGEST_LENGTH], MD4_CTX *ctx)
data/reaver-1.6.5/src/crypto/md5-internal.c:153:24: [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.
void MD5Final(unsigned char digest[16], struct MD5Context *ctx)
data/reaver-1.6.5/src/crypto/md5_i.h:27:24: [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.
void MD5Final(unsigned char digest[16], struct MD5Context *context);
data/reaver-1.6.5/src/crypto/ms_funcs.c:37:17: [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.
const unsigned char *addr[3];
data/reaver-1.6.5/src/crypto/ms_funcs.c:202:17: [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.
const unsigned char *addr1[3];
data/reaver-1.6.5/src/crypto/ms_funcs.c:204:17: [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.
const unsigned char *addr2[3];
data/reaver-1.6.5/src/crypto/ms_funcs.c:288:17: [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.
const unsigned char *addr[3];
data/reaver-1.6.5/src/crypto/ms_funcs.c:352:17: [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.
const unsigned char *addr[4];
data/reaver-1.6.5/src/crypto/sha1-internal.c:25:49: [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.
void SHA1Transform(u32 state[5], const unsigned char buffer[64]);
data/reaver-1.6.5/src/crypto/sha1-internal.c:177:49: [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.
void SHA1Transform(u32 state[5], const unsigned char buffer[64])
data/reaver-1.6.5/src/crypto/sha1-internal.c:181:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char c[64];
data/reaver-1.6.5/src/crypto/sha1-internal.c:279:25: [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.
void SHA1Final(unsigned char digest[20], SHA1_CTX* context)
data/reaver-1.6.5/src/crypto/sha1-internal.c:282: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.
unsigned char finalcount[8];
data/reaver-1.6.5/src/crypto/sha1-pbkdf2.c:26: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.
unsigned char tmp[SHA1_MAC_LEN], tmp2[SHA1_MAC_LEN];
data/reaver-1.6.5/src/crypto/sha1-pbkdf2.c:28: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.
unsigned char count_buf[4];
data/reaver-1.6.5/src/crypto/sha1-pbkdf2.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.
unsigned char digest[SHA1_MAC_LEN];
data/reaver-1.6.5/src/crypto/sha1-tlsprf.c:47:17: [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.
const unsigned char *SHA1_addr[3];
data/reaver-1.6.5/src/crypto/sha1-tprf.c:43:17: [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.
const unsigned char *addr[5];
data/reaver-1.6.5/src/crypto/sha1.c:35: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.
unsigned char k_pad[64]; /* padding - key XORd with ipad/opad */
data/reaver-1.6.5/src/crypto/sha1.c:36: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.
unsigned char tk[20];
data/reaver-1.6.5/src/crypto/sha1.c:134:17: [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.
const unsigned char *addr[3];
data/reaver-1.6.5/src/crypto/sha1_i.h:21: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.
unsigned char buffer[64];
data/reaver-1.6.5/src/crypto/sha1_i.h:26:25: [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.
void SHA1Final(unsigned char digest[20], struct SHA1Context *context);
data/reaver-1.6.5/src/crypto/sha1_i.h:27:49: [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.
void SHA1Transform(u32 state[5], const unsigned char buffer[64]);
data/reaver-1.6.5/src/crypto/sha256.c:34: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.
unsigned char k_pad[64]; /* padding - key XORd with ipad/opad */
data/reaver-1.6.5/src/crypto/sha256.c:35: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.
unsigned char tk[32];
data/reaver-1.6.5/src/crypto/tls_gnutls.c:504:2: [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[256];
data/reaver-1.6.5/src/crypto/tls_openssl.c:288:3: [2] (buffer) MultiByteToWideChar:
Requires maximum length in CHARACTERS, not bytes (CWE-120).
MultiByteToWideChar(CP_ACP, 0, name + 7, -1, wbuf, 255);
data/reaver-1.6.5/src/crypto/tls_openssl.c:424:2: [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[128];
data/reaver-1.6.5/src/crypto/tls_openssl.c:1165:2: [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[256];
data/reaver-1.6.5/src/crypto/tls_openssl.c:1623:2: [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[256];
data/reaver-1.6.5/src/crypto/tls_openssl.c:1698:6: [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(private_key, "rb");
data/reaver-1.6.5/src/crypto/tls_openssl.c:2473:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[100], *pos, *end;
data/reaver-1.6.5/src/defs.h:345: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.
unsigned char addr1[MAC_ADDR_LEN];
data/reaver-1.6.5/src/defs.h:346: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.
unsigned char addr2[MAC_ADDR_LEN];
data/reaver-1.6.5/src/defs.h:347: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.
unsigned char addr3[MAC_ADDR_LEN];
data/reaver-1.6.5/src/defs.h:373: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.
unsigned char timestamp[TIMESTAMP_LEN];
data/reaver-1.6.5/src/defs.h:383: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.
unsigned char org_code[3];
data/reaver-1.6.5/src/defs.h:404: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.
unsigned char id[3];
data/reaver-1.6.5/src/exchange.c:440:25: [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((void *) &element, (data + i), header_size);
data/reaver-1.6.5/src/globule.c:385:2: [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(globule->bssid, value, MAC_ADDR_LEN);
data/reaver-1.6.5/src/globule.c:394:2: [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(globule->mac, value, MAC_ADDR_LEN);
data/reaver-1.6.5/src/globule.c:543:2: [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(globule->htcaps, value, len);
data/reaver-1.6.5/src/globule.c:563:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(globule->ap_rates, value, len);
data/reaver-1.6.5/src/globule.c:585:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(globule->ap_ext_rates, value, len);
data/reaver-1.6.5/src/globule.c:625:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
if(is_set) memcpy(globule->vendor_oui+1, v, 3);
data/reaver-1.6.5/src/globule.h:47:9: [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 *p1[P1_SIZE]; /* Array of all possible values for the firt half of the pin */
data/reaver-1.6.5/src/globule.h:49:9: [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 *p2[P2_SIZE]; /* Array of all possible values for the second half of the pin */
data/reaver-1.6.5/src/globule.h:117:18: [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 bssid[MAC_ADDR_LEN]; /* Target BSSID */
data/reaver-1.6.5/src/globule.h:119:18: [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 mac[MAC_ADDR_LEN]; /* Source MAC address */
data/reaver-1.6.5/src/globule.h:121: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.
unsigned char vendor_oui[1+3]; /* the first byte contains 1 if set, 0 if not, the next 3 bytes the actual vendor OUI */
data/reaver-1.6.5/src/iface.c:151:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char chan_arg[32];
data/reaver-1.6.5/src/iface.c:152:3: [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(chan_arg, "-c%d", channel);
data/reaver-1.6.5/src/init.c:94:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(wpsconf->wps->uuid, DEFAULT_UUID, UUID_LEN);
data/reaver-1.6.5/src/init.c:107: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(wps->wps->dev.pri_dev_type, WPS_DEVICE_TYPE, WPS_DEV_TYPE_LEN);
data/reaver-1.6.5/src/init.c:108: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((void *) &wps->wps->dev.os_version, WPS_OS_VERSION, 4);
data/reaver-1.6.5/src/init.c:122:2: [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 errbuf[PCAP_ERRBUF_SIZE] = { 0 };
data/reaver-1.6.5/src/libwps/libwps.c:20:2: [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[512];
data/reaver-1.6.5/src/libwps/libwps.c:43:2: [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[1024];
data/reaver-1.6.5/src/libwps/libwps.c:353:6: [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(ptr, el, el_len);
data/reaver-1.6.5/src/libwps/libwps.c:406:6: [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(tag_data, (data+i+VENDOR_ID_OFFSET+WPS_VENDOR_ID_SIZE), tag_data_len);
data/reaver-1.6.5/src/libwps/libwps.c:441:33: [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(el_data, (data + offset + tag_size), el_data_size);
data/reaver-1.6.5/src/libwps/libwps.h:38:9: [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 manufacturer[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:39:9: [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 model_name[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:40:9: [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 model_number[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:41:9: [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 device_name[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:42:9: [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 ssid[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:43:9: [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 uuid[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:44:9: [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 serial[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:45:9: [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 selected_registrar[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:46:9: [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 response_type[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:47:9: [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 primary_device_type[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:48:9: [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 config_methods[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:49:9: [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 rf_bands[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:50:9: [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 os_version[LIBWPS_MAX_STR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:122:18: [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 addr1[MAC_ADDR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:123:18: [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 addr2[MAC_ADDR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:124:18: [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 addr3[MAC_ADDR_LEN];
data/reaver-1.6.5/src/libwps/libwps.h:130:18: [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 timestamp[TIMESTAMP_LEN];
data/reaver-1.6.5/src/lwe/iwlib.c:218:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(name, buf, (end - buf));
data/reaver-1.6.5/src/lwe/iwlib.c:239:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buff[1024];
data/reaver-1.6.5/src/lwe/iwlib.c:247: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).
fh = fopen(PROC_NET_DEV, "r");
data/reaver-1.6.5/src/lwe/iwlib.c:250: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).
fh = fopen(PROC_NET_WIRELESS, "r");
data/reaver-1.6.5/src/lwe/iwlib.c:264: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[IFNAMSIZ + 1];
data/reaver-1.6.5/src/lwe/iwlib.c:326:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buff[1024];
data/reaver-1.6.5/src/lwe/iwlib.c:332: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).
fh = fopen(PROC_NET_WIRELESS, "r");
data/reaver-1.6.5/src/lwe/iwlib.c:383:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[sizeof(iwrange) * 2]; /* Large enough */
data/reaver-1.6.5/src/lwe/iwlib.c:478:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[sizeof(iwrange) * 2]; /* Large enough */
data/reaver-1.6.5/src/lwe/iwlib.c:506: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((char *) range, buffer, sizeof(iwrange));
data/reaver-1.6.5/src/lwe/iwlib.c:514: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((char *) range,
data/reaver-1.6.5/src/lwe/iwlib.c:518: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((char *) range + iwr_off(num_channels),
data/reaver-1.6.5/src/lwe/iwlib.c:522: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((char *) range + iwr_off(sensitivity),
data/reaver-1.6.5/src/lwe/iwlib.c:526: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((char *) range + iwr_off(num_bitrates),
data/reaver-1.6.5/src/lwe/iwlib.c:530: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((char *) range + iwr_off(min_rts),
data/reaver-1.6.5/src/lwe/iwlib.c:534: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((char *) range + iwr_off(txpower_capa),
data/reaver-1.6.5/src/lwe/iwlib.c:538: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((char *) range + iwr_off(txpower),
data/reaver-1.6.5/src/lwe/iwlib.c:542: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((char *) range + iwr_off(avg_qual),
data/reaver-1.6.5/src/lwe/iwlib.c:690: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(&(info->nwid), &(wrq.u.nwid), sizeof(iwparam));
data/reaver-1.6.5/src/lwe/iwlib.c:828: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(&(wrq.u.nwid), &(info->nwid), sizeof(iwparam));
data/reaver-1.6.5/src/lwe/iwlib.c:1046:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char vbuf[16];
data/reaver-1.6.5/src/lwe/iwlib.c:1288:18: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FILE * f = fopen(PROC_NET_WIRELESS, "r");
data/reaver-1.6.5/src/lwe/iwlib.c:1289:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[256];
data/reaver-1.6.5/src/lwe/iwlib.c:1519:2: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "on"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1522:4: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "**"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1528:8: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "**"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1536: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(buffer, "%.2X", key[0]); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1542:4: [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(buffer, "%.2X", key[i]); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1582: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(key, input + 2, keylen);
data/reaver-1.6.5/src/lwe/iwlib.c:1594: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.
unsigned char out[IW_ENCODING_TOKEN_MAX];
data/reaver-1.6.5/src/lwe/iwlib.c:1641:2: [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(key, out, keylen);
data/reaver-1.6.5/src/lwe/iwlib.c:1646:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[IW_ENCODING_TOKEN_MAX * 3];
data/reaver-1.6.5/src/lwe/iwlib.c:1679: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(key, input + 2, keylen);
data/reaver-1.6.5/src/lwe/iwlib.c:1743:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " min"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1748:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " max"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1755:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " timeout:"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1762:4: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " saving:"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1767:4: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " period:"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1812:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "mode:Unicast only received"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1815:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "mode:Multicast only received"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1818:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "mode:All packets received"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1821:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "mode:Force sending"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1824:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "mode:Repeat multicasts"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1856:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " min"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1861:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " max"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1866:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " short"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1871:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " long"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1878:7: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, " lifetime:"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1957:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[20];
data/reaver-1.6.5/src/lwe/iwlib.c:2037:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(eth->ether_addr_octet, ifr.ifr_hwaddr.sa_data, 6);
data/reaver-1.6.5/src/lwe/iwlib.c:2060:3: [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(buf, "%02X", mac[0]);
data/reaver-1.6.5/src/lwe/iwlib.c:2064:5: [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(buf + (i * 3) - 1, ":%02X", mac[i]);
data/reaver-1.6.5/src/lwe/iwlib.c:2077:3: [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(buf, "%02X:%02X:%02X:%02X:%02X:%02X",
data/reaver-1.6.5/src/lwe/iwlib.c:2099:5: [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(buf, "Not-Associated");
data/reaver-1.6.5/src/lwe/iwlib.c:2102: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(buf, "Invalid");
data/reaver-1.6.5/src/lwe/iwlib.c:2105:2: [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(buf, "None");
data/reaver-1.6.5/src/lwe/iwlib.c:2144: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[20];
data/reaver-1.6.5/src/lwe/iwlib.c:2225:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((char *) &sain->sin_addr, (char *) hp->h_addr_list[0], hp->h_length);
data/reaver-1.6.5/src/lwe/iwlib.c:2262: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((char *) &(arp_query.arp_pa),
data/reaver-1.6.5/src/lwe/iwlib.c:2279: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((char *) sap,
data/reaver-1.6.5/src/lwe/iwlib.c:2285:2: [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[20];
data/reaver-1.6.5/src/lwe/iwlib.c:2310:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[20];
data/reaver-1.6.5/src/lwe/iwlib.c:2742:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy((char *) iwe, stream->current, IW_EV_LCP_PK_LEN);
data/reaver-1.6.5/src/lwe/iwlib.c:2804: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((char *) iwe + IW_EV_LCP_LEN + IW_EV_POINT_OFF,
data/reaver-1.6.5/src/lwe/iwlib.c:2807: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((char *) iwe + IW_EV_LCP_LEN, pointer, event_len);
data/reaver-1.6.5/src/lwe/iwlib.c:2850:9: [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((char *) iwe + IW_EV_LCP_LEN + IW_EV_POINT_OFF,
data/reaver-1.6.5/src/lwe/iwlib.c:2900: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((char *) iwe + IW_EV_LCP_LEN, pointer, event_len);
data/reaver-1.6.5/src/lwe/iwlib.c:2976: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(&(wscan->ap_addr), &(event->u.ap_addr), sizeof (sockaddr));
data/reaver-1.6.5/src/lwe/iwlib.c:2980: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(&(wscan->b.nwid), &(event->u.nwid), sizeof(iwparam));
data/reaver-1.6.5/src/lwe/iwlib.c:2997:2: [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(wscan->b.essid, event->u.essid.pointer, event->u.essid.length);
data/reaver-1.6.5/src/lwe/iwlib.c:3004:2: [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(wscan->b.key, event->u.essid.pointer, event->u.data.length);
data/reaver-1.6.5/src/lwe/iwlib.c:3011: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(&wscan->stats.qual, &event->u.qual, sizeof(struct iw_quality));
data/reaver-1.6.5/src/lwe/iwlib.c:3020: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(&(wscan->maxbitrate), &(event->u.bitrate), sizeof(iwparam));
data/reaver-1.6.5/src/lwe/iwlib.h:175:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[IFNAMSIZ + 1]; /* Wireless/protocol name */
data/reaver-1.6.5/src/lwe/iwlib.h:182:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char key[IW_ENCODING_TOKEN_MAX]; /* Encoding key used */
data/reaver-1.6.5/src/lwe/iwlib.h:187:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char essid[IW_ESSID_MAX_SIZE + 1]; /* ESSID (extended network) */
data/reaver-1.6.5/src/lwe/iwlib.h:201:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char nickname[IW_ESSID_MAX_SIZE + 1]; /* NickName */
data/reaver-1.6.5/src/lwe/iwlib.h:282:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char cmd[8]; /* Short name */
data/reaver-1.6.5/src/lwe/wireless.21.h:905:2: [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[IFNAMSIZ];
data/reaver-1.6.5/src/lwe/wireless.21.h:944:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char ifrn_name[IFNAMSIZ]; /* if name, e.g. "eth0" */
data/reaver-1.6.5/src/lwe/wireless.21.h:1079:2: [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[IFNAMSIZ]; /* Name of the extension */
data/reaver-1.6.5/src/misc.c:39:2: [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 nyu[6*3];
data/reaver-1.6.5/src/pins.c:53:70: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
snprintf(pin, pin_len, "%s%d", key, wps_pin_checksum(atoi(key)));
data/reaver-1.6.5/src/pixie.c:13:3: [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", in[i]);
data/reaver-1.6.5/src/pixie.c:23:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char cmd[4096];
data/reaver-1.6.5/src/radiotap_flags.h:126:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&fc, data + *offset, 4);
data/reaver-1.6.5/src/send.c:158:17: [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 unsigned char last_packet[4096];
data/reaver-1.6.5/src/send.c:178: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(last_packet, packet, len);
data/reaver-1.6.5/src/session.c:56:2: [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 line[MAX_LINE_SIZE] = { 0 };
data/reaver-1.6.5/src/session.c:57:2: [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 temp[P1_READ_LEN] = { 0 };
data/reaver-1.6.5/src/session.c:58:2: [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[FILENAME_MAX];
data/reaver-1.6.5/src/session.c:111:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if((fp = fopen(file, "r")))
data/reaver-1.6.5/src/session.c:116:19: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_p1_index(atoi(line));
data/reaver-1.6.5/src/session.c:122:20: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_p2_index(atoi(line));
data/reaver-1.6.5/src/session.c:128:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_key_status(atoi(line));
data/reaver-1.6.5/src/session.c:186:9: [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_name[FILENAME_MAX] = { 0 };
data/reaver-1.6.5/src/session.c:187:9: [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 line[MAX_LINE_SIZE] = { 0 };
data/reaver-1.6.5/src/session.c:234:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if((fp = fopen(file_name, "w")))
data/reaver-1.6.5/src/tls/pkcs5.c:57:2: [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 obuf[80];
data/reaver-1.6.5/src/tls/pkcs8.c:31:2: [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 obuf[80];
data/reaver-1.6.5/src/tls/tlsv1_cred.c:50:2: [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[128];
data/reaver-1.6.5/src/tls/x509v3.c:939:2: [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[80];
data/reaver-1.6.5/src/tls/x509v3.c:1120:2: [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[80];
data/reaver-1.6.5/src/tls/x509v3.c:1232:2: [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 sbuf[128];
data/reaver-1.6.5/src/tls/x509v3.c:1842:2: [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[128];
data/reaver-1.6.5/src/utils/base64.c:20:23: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const unsigned char base64_table[65] =
data/reaver-1.6.5/src/utils/base64.c:106: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.
unsigned char dtable[256], *out, *pos, in[4], block[4], tmp;
data/reaver-1.6.5/src/utils/common.c:345:9: [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 ssid_txt[33];
data/reaver-1.6.5/src/utils/common.c:373:4: [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(new + j, "\\\\x%02x", s[i] & 0xff);
data/reaver-1.6.5/src/utils/file.c:7:2: [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[256];
data/reaver-1.6.5/src/utils/file.c:8:2: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buf, "/tmp/reaver-XXXXXX");
data/reaver-1.6.5/src/utils/file.c:12:2: [2] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant string.
strcat(buf, ".tmp");
data/reaver-1.6.5/src/utils/file.c:17:12: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FILE *f = fopen(fn, "w");
data/reaver-1.6.5/src/utils/os.h:407:28: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
#define os_memcpy(d, s, n) memcpy((d), (s), (n))
data/reaver-1.6.5/src/utils/os.h:483:9: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
#define memcpy OS_DO_NOT_USE_memcpy
data/reaver-1.6.5/src/utils/os_internal.c:81:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FILE *f = fopen(pid_file, "w");
data/reaver-1.6.5/src/utils/os_internal.c:104:6: [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("/dev/urandom", "rb");
data/reaver-1.6.5/src/utils/os_internal.c:195:6: [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(name, "rb");
data/reaver-1.6.5/src/utils/os_unix.c:110:12: [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).
devnull = open("/dev/null", O_RDWR);
data/reaver-1.6.5/src/utils/os_unix.c:147:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FILE *f = fopen(pid_file, "w");
data/reaver-1.6.5/src/utils/os_unix.c:171:6: [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("/dev/urandom", "rb");
data/reaver-1.6.5/src/utils/os_unix.c:289:6: [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(name, "rb");
data/reaver-1.6.5/src/utils/os_win32.c:173:6: [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(name, "rb");
data/reaver-1.6.5/src/utils/pcsc_funcs.c:334:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char rid[5];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:335:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char appl_code[2]; /* 0x1002 for 3G USIM */
data/reaver-1.6.5/src/utils/pcsc_funcs.c:337: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.
unsigned char buf[100];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:444: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.
unsigned char buf[100];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:557:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char aid[32];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:707: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.
unsigned char resp[3];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:708: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.
unsigned char cmd[50] = { SIM_CMD_SELECT };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:710: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.
unsigned char get_resp[5] = { SIM_CMD_GET_RESPONSE };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:793: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.
unsigned char buf[255];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:794: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.
unsigned char cmd[5] = { SIM_CMD_READ_RECORD /* , len */ };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:829: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.
unsigned char cmd[5] = { SIM_CMD_READ_RECORD /* , len */ };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:875: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.
unsigned char cmd[5] = { SIM_CMD_READ_BIN /* , len */ };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:919: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.
unsigned char resp[3];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:920: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.
unsigned char cmd[5 + 8] = { SIM_CMD_VERIFY_CHV1 };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:964: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.
unsigned char buf[100];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:1044: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.
unsigned char cmd[5 + 1 + 16] = { SIM_CMD_RUN_GSM_ALG };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:1046: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.
unsigned char get_resp[5] = { SIM_CMD_GET_RESPONSE };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:1047: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.
unsigned char resp[3], buf[12 + 3 + 2];
data/reaver-1.6.5/src/utils/pcsc_funcs.c:1144: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.
unsigned char cmd[5 + 1 + AKA_RAND_LEN + 1 + AKA_AUTN_LEN] =
data/reaver-1.6.5/src/utils/pcsc_funcs.c:1146: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.
unsigned char get_resp[5] = { USIM_CMD_GET_RESPONSE };
data/reaver-1.6.5/src/utils/pcsc_funcs.c:1147: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.
unsigned char resp[3], buf[64], *pos, *end;
data/reaver-1.6.5/src/utils/trace.c:39:2: [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 exe[50], fname[512];
data/reaver-1.6.5/src/utils/vendor.c:6:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char id[3];
data/reaver-1.6.5/src/utils/vendor.c:7:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[VENDOR_STR_SIZE];
data/reaver-1.6.5/src/utils/wpa_debug.c:290:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
out_file = fopen(path, "a");
data/reaver-1.6.5/src/wps/wps.c:461:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char devtype[WPS_DEV_TYPE_BUFSIZE];
data/reaver-1.6.5/src/wps/wps.h:52:2: [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 ssid[32];
data/reaver-1.6.5/src/wps/wps.h:730:32: [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.
int wps_dev_type_str2bin(const char *str, u8 dev_type[WPS_DEV_TYPE_LEN]);
data/reaver-1.6.5/src/wps/wps.h:731:1: [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 * wps_dev_type_bin2str(const u8 dev_type[WPS_DEV_TYPE_LEN], char *buf,
data/reaver-1.6.5/src/wps/wps_attr_build.c:66: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[1024];
data/reaver-1.6.5/src/wps/wps_common.c:134:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[4096];
data/reaver-1.6.5/src/wps/wps_common.c:544:32: [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.
int wps_dev_type_str2bin(const char *str, u8 dev_type[WPS_DEV_TYPE_LEN])
data/reaver-1.6.5/src/wps/wps_common.c:549:25: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
WPA_PUT_BE16(dev_type, atoi(str));
data/reaver-1.6.5/src/wps/wps_common.c:560:29: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
WPA_PUT_BE16(&dev_type[6], atoi(pos));
data/reaver-1.6.5/src/wps/wps_common.c:567:1: [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 * wps_dev_type_bin2str(const u8 dev_type[WPS_DEV_TYPE_LEN], char *buf,
data/reaver-1.6.5/src/wps/wps_dev_attr.c:289:2: [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 devtype[WPS_DEV_TYPE_BUFSIZE];
data/reaver-1.6.5/src/wps/wps_registrar.c:1321:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char hex[65];
data/reaver-1.6.5/src/wps/wps_registrar.c:1331:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char hex[65];
data/reaver-1.6.5/src/wps/wps_registrar.c:1700:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[2048];
data/reaver-1.6.5/src/wps/wps_registrar.c:1764:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[2048];
data/reaver-1.6.5/src/wps/wps_registrar.c:1784:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[2048];
data/reaver-1.6.5/src/wps/wps_registrar.c:1924:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[2048];
data/reaver-1.6.5/src/wps/wps_registrar.c:2985:2: [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 uuid[40];
data/reaver-1.6.5/src/wps/wps_registrar.c:2986:2: [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 devtype[WPS_DEV_TYPE_BUFSIZE];
data/reaver-1.6.5/src/wps/wps_ufd.c:45:2: [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 ext[5];
data/reaver-1.6.5/src/wps/wps_ufd.c:92: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 temp[128];
data/reaver-1.6.5/src/wps/wps_ufd.c:130:2: [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 temp[128];
data/reaver-1.6.5/src/wps/wps_ufd.c:132:2: [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 filename[13];
data/reaver-1.6.5/src/wps/wps_ufd.c:158:12: [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).
ufd_fd = open(temp, O_WRONLY | O_CREAT | O_TRUNC,
data/reaver-1.6.5/src/wps/wps_ufd.c:161:12: [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).
ufd_fd = open(temp, O_RDONLY);
data/reaver-1.6.5/src/wpsmon.c:49: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.
unsigned char mac[6];
data/reaver-1.6.5/src/wpsmon.c:50: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.
unsigned char vendor_oui[1+3];
data/reaver-1.6.5/src/wpsmon.c:61: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.
unsigned char mac[6];
data/reaver-1.6.5/src/wpsmon.c:66:2: [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(seen_list[seen_count].mac, mac, 6);
data/reaver-1.6.5/src/wpsmon.c:160:15: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
channel = atoi(optarg);
data/reaver-1.6.5/src/wpsmon.c:170:24: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
set_max_num_probes(atoi(optarg));
data/reaver-1.6.5/src/argsparser.c:245: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).
for (i = 0; i < strlen(pin); i++)
data/reaver-1.6.5/src/argsparser.c:250: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(pin) == 8)
data/reaver-1.6.5/src/argsparser.c:271:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(pin);
data/reaver-1.6.5/src/builder.c:115:28: [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).
ssid_tag.len = (uint8_t) strlen(essid);
data/reaver-1.6.5/src/builder.c:416:20: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size_t ssid_len = strlen(essid), ssid_param_len;
data/reaver-1.6.5/src/crypto/tls_gnutls.c:486:4: [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((char *) gen->d.ia5->data) + 1;
data/reaver-1.6.5/src/globule.c:411:6: [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(value) > 0)
data/reaver-1.6.5/src/iface.c:83:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(ifr.ifr_name, get_iface(), IFNAMSIZ);
data/reaver-1.6.5/src/libwps/libwps.c:357:6: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(ptr, src, LIBWPS_MAX_STR_LEN);
data/reaver-1.6.5/src/lwe/iwlib.c:682:7: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(info->name, wrq.u.name, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:762:7: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(wrq.ifr_ifrn.ifrn_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:849:28: [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).
wrq.u.essid.length = strlen(info->essid);
data/reaver-1.6.5/src/lwe/iwlib.c:893:35: [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( (!strncmp(protocol1, dot11, strlen(dot11))) &&
data/reaver-1.6.5/src/lwe/iwlib.c:894:35: [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).
(!strncmp(protocol2, dot11, strlen(dot11))) )
data/reaver-1.6.5/src/lwe/iwlib.c:896:39: [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 * sub1 = protocol1 + strlen(dot11);
data/reaver-1.6.5/src/lwe/iwlib.c:897:39: [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 * sub2 = protocol2 + strlen(dot11);
data/reaver-1.6.5/src/lwe/iwlib.c:905:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
for(i = 0; i < strlen(dot11_ds); i++)
data/reaver-1.6.5/src/lwe/iwlib.c:916:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
for(i = 0; i < strlen(dot11_5g); i++)
data/reaver-1.6.5/src/lwe/iwlib.c:1279:7: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(wrq.ifr_ifrn.ifrn_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:1302: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).
if(strncmp(bp,ifname,strlen(ifname))==0 && bp[strlen(ifname)]==':')
data/reaver-1.6.5/src/lwe/iwlib.c:1302: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).
if(strncmp(bp,ifname,strlen(ifname))==0 && bp[strlen(ifname)]==':')
data/reaver-1.6.5/src/lwe/iwlib.c:1527:3: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
strcpy(buffer++, "-"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1541:6: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
strcpy(buffer++, "-"); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1579: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).
keylen = strlen(input + 2); /* skip "s:" */
data/reaver-1.6.5/src/lwe/iwlib.c:1675: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).
keylen = strlen(input + 2) + 1; /* skip "l:", add '\0' */
data/reaver-1.6.5/src/lwe/iwlib.c:1827:7: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
strcpy(buffer, ""); /* Size checked */
data/reaver-1.6.5/src/lwe/iwlib.c:1944:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(ifr.ifr_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:1978:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(ifr.ifr_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:2032:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(ifr.ifr_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:2269:7: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(arp_query.arp_dev, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.c:3219:7: [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(delay * 1000);
data/reaver-1.6.5/src/lwe/iwlib.h:513:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(pwrq->ifr_ifrn.ifrn_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/lwe/iwlib.h:529:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(pwrq->ifr_ifrn.ifrn_name, ifname, IFNAMSIZ);
data/reaver-1.6.5/src/pins.c:79:97: [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).
add_result = wps_registrar_add_pin(wps->wps->registrar, NULL, (const u8 *) pin, strlen(pin), 0);
data/reaver-1.6.5/src/send.c:76:38: [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).
packet = build_eap_packet(identity, strlen(identity), &packet_len);
data/reaver-1.6.5/src/session.c:105:13: [1] (buffer) getc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
answer = getc(stdin);
data/reaver-1.6.5/src/session.c:237:18: [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).
write_size = strlen(line);
data/reaver-1.6.5/src/session.c:244:19: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
write_size = strlen(line);
data/reaver-1.6.5/src/session.c:251: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).
write_size = strlen(line);
data/reaver-1.6.5/src/session.c:259: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).
fwrite(get_p1(i), 1, strlen(get_p1(i)), fp);
data/reaver-1.6.5/src/session.c:266: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).
fwrite(get_p2(i), 1, strlen(get_p2(i)), fp);
data/reaver-1.6.5/src/session.c:271:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if(wpa_key && strlen(wpa_key) > 0)
data/reaver-1.6.5/src/session.c:288: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(!essid || strlen(essid) == 0)
data/reaver-1.6.5/src/utils/common.c:317:19: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
buf = os_malloc((strlen(str) + 1) * sizeof(TCHAR));
data/reaver-1.6.5/src/utils/common.c:367:18: [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 i,j, l = strlen(s), ls=l;
data/reaver-1.6.5/src/utils/common.c:387:11: [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(!s || strlen(s)>32) { //32 characters
data/reaver-1.6.5/src/utils/file.c:18: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).
size_t l = strlen(contents);
data/reaver-1.6.5/src/utils/os.h:420:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
#define os_strlen(s) strlen(s)
data/reaver-1.6.5/src/utils/os.h:446:29: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
#define os_strncpy(d, s, n) strncpy((d), (s), (n))
data/reaver-1.6.5/src/utils/os.h:489:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
#define strlen OS_DO_NOT_USE_strlen
data/reaver-1.6.5/src/utils/os.h:498:8: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
#undef strncpy
data/reaver-1.6.5/src/utils/os.h:499:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
#define strncpy OS_DO_NOT_USE_strncpy
data/reaver-1.6.5/src/utils/os_internal.c:35:3: [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(usec);
data/reaver-1.6.5/src/utils/os_internal.c:147:12: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
cwd_len = strlen(cwd);
data/reaver-1.6.5/src/utils/os_internal.c:148:12: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
rel_len = strlen(rel_path);
data/reaver-1.6.5/src/utils/os_unix.c:46:3: [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(usec);
data/reaver-1.6.5/src/wps/wps_ufd.c:47:6: [1] (buffer) sscanf:
It's unclear if the %s limit in the format string is small enough
(CWE-120). Check that the limit is sufficiently small, or use a different
input function.
if (sscanf(entry->d_name, "%8x.%4s", &prefix, ext) != 2)
data/reaver-1.6.5/src/wps/wps_ufd.c:196:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read(data->ufd_fd, wpabuf_mhead(buf), file_size) !=
data/reaver-1.6.5/src/wpsmon.c:246: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).
(last_optarg && (memcmp(argv[i], last_optarg, strlen(last_optarg)) == 0))
ANALYSIS SUMMARY:
Hits = 536
Lines analyzed = 76132 in approximately 1.79 seconds (42486 lines/second)
Physical Source Lines of Code (SLOC) = 55158
Hits@level = [0] 264 [1] 59 [2] 346 [3] 10 [4] 120 [5] 1
Hits@level+ = [0+] 800 [1+] 536 [2+] 477 [3+] 131 [4+] 121 [5+] 1
Hits/KSLOC@level+ = [0+] 14.5038 [1+] 9.71754 [2+] 8.64788 [3+] 2.375 [4+] 2.1937 [5+] 0.0181297
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.