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/bully-1.4.00/src/80211.c
Examining data/bully-1.4.00/src/80211.h
Examining data/bully-1.4.00/src/bswap.h
Examining data/bully-1.4.00/src/bully.c
Examining data/bully-1.4.00/src/bully.h
Examining data/bully-1.4.00/src/common/defs.h
Examining data/bully-1.4.00/src/common/eapol_common.h
Examining data/bully-1.4.00/src/common/ieee802_11_common.c
Examining data/bully-1.4.00/src/common/ieee802_11_common.h
Examining data/bully-1.4.00/src/common/ieee802_11_defs.h
Examining data/bully-1.4.00/src/common/privsep_commands.h
Examining data/bully-1.4.00/src/common/version.h
Examining data/bully-1.4.00/src/common/wpa_common.c
Examining data/bully-1.4.00/src/common/wpa_common.h
Examining data/bully-1.4.00/src/common/wpa_ctrl.c
Examining data/bully-1.4.00/src/common/wpa_ctrl.h
Examining data/bully-1.4.00/src/crc32.c
Examining data/bully-1.4.00/src/crypto/aes-cbc.c
Examining data/bully-1.4.00/src/crypto/aes-ctr.c
Examining data/bully-1.4.00/src/crypto/aes-eax.c
Examining data/bully-1.4.00/src/crypto/aes-encblock.c
Examining data/bully-1.4.00/src/crypto/aes-internal-dec.c
Examining data/bully-1.4.00/src/crypto/aes-internal-enc.c
Examining data/bully-1.4.00/src/crypto/aes-internal.c
Examining data/bully-1.4.00/src/crypto/aes-omac1.c
Examining data/bully-1.4.00/src/crypto/aes-unwrap.c
Examining data/bully-1.4.00/src/crypto/aes-wrap.c
Examining data/bully-1.4.00/src/crypto/aes.h
Examining data/bully-1.4.00/src/crypto/aes_i.h
Examining data/bully-1.4.00/src/crypto/aes_wrap.h
Examining data/bully-1.4.00/src/crypto/crypto.h
Examining data/bully-1.4.00/src/crypto/crypto_cryptoapi.c
Examining data/bully-1.4.00/src/crypto/crypto_gnutls.c
Examining data/bully-1.4.00/src/crypto/crypto_internal-cipher.c
Examining data/bully-1.4.00/src/crypto/crypto_internal-modexp.c
Examining data/bully-1.4.00/src/crypto/crypto_internal-rsa.c
Examining data/bully-1.4.00/src/crypto/crypto_internal.c
Examining data/bully-1.4.00/src/crypto/crypto_libtomcrypt.c
Examining data/bully-1.4.00/src/crypto/crypto_none.c
Examining data/bully-1.4.00/src/crypto/crypto_nss.c
Examining data/bully-1.4.00/src/crypto/crypto_openssl.c
Examining data/bully-1.4.00/src/crypto/des-internal.c
Examining data/bully-1.4.00/src/crypto/des_i.h
Examining data/bully-1.4.00/src/crypto/dh_group5.c
Examining data/bully-1.4.00/src/crypto/dh_group5.h
Examining data/bully-1.4.00/src/crypto/dh_groups.c
Examining data/bully-1.4.00/src/crypto/dh_groups.h
Examining data/bully-1.4.00/src/crypto/fips_prf_cryptoapi.c
Examining data/bully-1.4.00/src/crypto/fips_prf_gnutls.c
Examining data/bully-1.4.00/src/crypto/fips_prf_internal.c
Examining data/bully-1.4.00/src/crypto/fips_prf_nss.c
Examining data/bully-1.4.00/src/crypto/fips_prf_openssl.c
Examining data/bully-1.4.00/src/crypto/md4-internal.c
Examining data/bully-1.4.00/src/crypto/md5-internal.c
Examining data/bully-1.4.00/src/crypto/md5-non-fips.c
Examining data/bully-1.4.00/src/crypto/md5.c
Examining data/bully-1.4.00/src/crypto/md5.h
Examining data/bully-1.4.00/src/crypto/md5_i.h
Examining data/bully-1.4.00/src/crypto/milenage.c
Examining data/bully-1.4.00/src/crypto/milenage.h
Examining data/bully-1.4.00/src/crypto/ms_funcs.c
Examining data/bully-1.4.00/src/crypto/ms_funcs.h
Examining data/bully-1.4.00/src/crypto/rc4.c
Examining data/bully-1.4.00/src/crypto/sha1-internal.c
Examining data/bully-1.4.00/src/crypto/sha1-pbkdf2.c
Examining data/bully-1.4.00/src/crypto/sha1-tlsprf.c
Examining data/bully-1.4.00/src/crypto/sha1-tprf.c
Examining data/bully-1.4.00/src/crypto/sha1.c
Examining data/bully-1.4.00/src/crypto/sha1.h
Examining data/bully-1.4.00/src/crypto/sha1_i.h
Examining data/bully-1.4.00/src/crypto/sha256-internal.c
Examining data/bully-1.4.00/src/crypto/sha256.c
Examining data/bully-1.4.00/src/crypto/sha256.h
Examining data/bully-1.4.00/src/crypto/tls.h
Examining data/bully-1.4.00/src/crypto/tls_gnutls.c
Examining data/bully-1.4.00/src/crypto/tls_internal.c
Examining data/bully-1.4.00/src/crypto/tls_none.c
Examining data/bully-1.4.00/src/crypto/tls_nss.c
Examining data/bully-1.4.00/src/crypto/tls_openssl.c
Examining data/bully-1.4.00/src/crypto/tls_schannel.c
Examining data/bully-1.4.00/src/frame.c
Examining data/bully-1.4.00/src/frame.h
Examining data/bully-1.4.00/src/iface.c
Examining data/bully-1.4.00/src/iface.h
Examining data/bully-1.4.00/src/luaclib.c
Examining data/bully-1.4.00/src/luaclib.h
Examining data/bully-1.4.00/src/pdust.c
Examining data/bully-1.4.00/src/pdust.h
Examining data/bully-1.4.00/src/pingen.c
Examining data/bully-1.4.00/src/pingen.h
Examining data/bully-1.4.00/src/pixie.h
Examining data/bully-1.4.00/src/timer.c
Examining data/bully-1.4.00/src/tls/asn1.c
Examining data/bully-1.4.00/src/tls/asn1.h
Examining data/bully-1.4.00/src/tls/bignum.c
Examining data/bully-1.4.00/src/tls/bignum.h
Examining data/bully-1.4.00/src/tls/libtommath.c
Examining data/bully-1.4.00/src/tls/pkcs1.c
Examining data/bully-1.4.00/src/tls/pkcs1.h
Examining data/bully-1.4.00/src/tls/pkcs5.c
Examining data/bully-1.4.00/src/tls/pkcs5.h
Examining data/bully-1.4.00/src/tls/pkcs8.c
Examining data/bully-1.4.00/src/tls/pkcs8.h
Examining data/bully-1.4.00/src/tls/rsa.c
Examining data/bully-1.4.00/src/tls/rsa.h
Examining data/bully-1.4.00/src/tls/tlsv1_client.c
Examining data/bully-1.4.00/src/tls/tlsv1_client.h
Examining data/bully-1.4.00/src/tls/tlsv1_client_i.h
Examining data/bully-1.4.00/src/tls/tlsv1_client_read.c
Examining data/bully-1.4.00/src/tls/tlsv1_client_write.c
Examining data/bully-1.4.00/src/tls/tlsv1_common.c
Examining data/bully-1.4.00/src/tls/tlsv1_common.h
Examining data/bully-1.4.00/src/tls/tlsv1_cred.c
Examining data/bully-1.4.00/src/tls/tlsv1_cred.h
Examining data/bully-1.4.00/src/tls/tlsv1_record.c
Examining data/bully-1.4.00/src/tls/tlsv1_record.h
Examining data/bully-1.4.00/src/tls/tlsv1_server.c
Examining data/bully-1.4.00/src/tls/tlsv1_server.h
Examining data/bully-1.4.00/src/tls/tlsv1_server_i.h
Examining data/bully-1.4.00/src/tls/tlsv1_server_read.c
Examining data/bully-1.4.00/src/tls/tlsv1_server_write.c
Examining data/bully-1.4.00/src/tls/x509v3.c
Examining data/bully-1.4.00/src/tls/x509v3.h
Examining data/bully-1.4.00/src/utils.c
Examining data/bully-1.4.00/src/utils/base64.c
Examining data/bully-1.4.00/src/utils/base64.h
Examining data/bully-1.4.00/src/utils/build_config.h
Examining data/bully-1.4.00/src/utils/common.c
Examining data/bully-1.4.00/src/utils/common.h
Examining data/bully-1.4.00/src/utils/eloop.c
Examining data/bully-1.4.00/src/utils/eloop.h
Examining data/bully-1.4.00/src/utils/eloop_none.c
Examining data/bully-1.4.00/src/utils/eloop_win.c
Examining data/bully-1.4.00/src/utils/includes.h
Examining data/bully-1.4.00/src/utils/ip_addr.c
Examining data/bully-1.4.00/src/utils/ip_addr.h
Examining data/bully-1.4.00/src/utils/list.h
Examining data/bully-1.4.00/src/utils/os.h
Examining data/bully-1.4.00/src/utils/os_internal.c
Examining data/bully-1.4.00/src/utils/os_none.c
Examining data/bully-1.4.00/src/utils/os_unix.c
Examining data/bully-1.4.00/src/utils/os_win32.c
Examining data/bully-1.4.00/src/utils/pcsc_funcs.c
Examining data/bully-1.4.00/src/utils/pcsc_funcs.h
Examining data/bully-1.4.00/src/utils/radiotap.c
Examining data/bully-1.4.00/src/utils/radiotap.h
Examining data/bully-1.4.00/src/utils/radiotap_iter.h
Examining data/bully-1.4.00/src/utils/state_machine.h
Examining data/bully-1.4.00/src/utils/trace.c
Examining data/bully-1.4.00/src/utils/trace.h
Examining data/bully-1.4.00/src/utils/uuid.c
Examining data/bully-1.4.00/src/utils/uuid.h
Examining data/bully-1.4.00/src/utils/wpa_debug.c
Examining data/bully-1.4.00/src/utils/wpa_debug.h
Examining data/bully-1.4.00/src/utils/wpabuf.c
Examining data/bully-1.4.00/src/utils/wpabuf.h
Examining data/bully-1.4.00/src/version.h
Examining data/bully-1.4.00/src/wps/http.h
Examining data/bully-1.4.00/src/wps/http_client.c
Examining data/bully-1.4.00/src/wps/http_client.h
Examining data/bully-1.4.00/src/wps/http_server.c
Examining data/bully-1.4.00/src/wps/http_server.h
Examining data/bully-1.4.00/src/wps/httpread.c
Examining data/bully-1.4.00/src/wps/httpread.h
Examining data/bully-1.4.00/src/wps/ndef.c
Examining data/bully-1.4.00/src/wps/pixie.h
Examining data/bully-1.4.00/src/wps/upnp_xml.c
Examining data/bully-1.4.00/src/wps/upnp_xml.h
Examining data/bully-1.4.00/src/wps/wps.c
Examining data/bully-1.4.00/src/wps/wps.h
Examining data/bully-1.4.00/src/wps/wps_attr_build.c
Examining data/bully-1.4.00/src/wps/wps_attr_parse.c
Examining data/bully-1.4.00/src/wps/wps_attr_process.c
Examining data/bully-1.4.00/src/wps/wps_common.c
Examining data/bully-1.4.00/src/wps/wps_defs.h
Examining data/bully-1.4.00/src/wps/wps_dev_attr.c
Examining data/bully-1.4.00/src/wps/wps_dev_attr.h
Examining data/bully-1.4.00/src/wps/wps_enrollee.c
Examining data/bully-1.4.00/src/wps/wps_er.c
Examining data/bully-1.4.00/src/wps/wps_er.h
Examining data/bully-1.4.00/src/wps/wps_er_ssdp.c
Examining data/bully-1.4.00/src/wps/wps_i.h
Examining data/bully-1.4.00/src/wps/wps_nfc.c
Examining data/bully-1.4.00/src/wps/wps_nfc_pn531.c
Examining data/bully-1.4.00/src/wps/wps_registrar.c
Examining data/bully-1.4.00/src/wps/wps_ufd.c
Examining data/bully-1.4.00/src/wps/wps_upnp.c
Examining data/bully-1.4.00/src/wps/wps_upnp.h
Examining data/bully-1.4.00/src/wps/wps_upnp_ap.c
Examining data/bully-1.4.00/src/wps/wps_upnp_event.c
Examining data/bully-1.4.00/src/wps/wps_upnp_i.h
Examining data/bully-1.4.00/src/wps/wps_upnp_ssdp.c
Examining data/bully-1.4.00/src/wps/wps_upnp_web.c

FINAL RESULTS:

data/bully-1.4.00/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/bully-1.4.00/src/bully.c:185: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(G->warpath, temp);
data/bully-1.4.00/src/bully.c:187:3:  [4] (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).
		strcat(G->warpath, EXE_NAME);
data/bully-1.4.00/src/bully.c:373:10:  [4] (buffer) sscanf:
  The scanf() family's %s operation, without a limit specification, permits
  buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
  different input function.
					if (sscanf(optarg, "%d,%d%s", &G->k1delay, &G->k1step, G->error) != 2) {
data/bully-1.4.00/src/bully.c:380:10:  [4] (buffer) sscanf:
  The scanf() family's %s operation, without a limit specification, permits
  buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
  different input function.
					if (sscanf(optarg, "%d,%d%s", &G->k2delay, &G->k2step, G->error) != 2) {
data/bully-1.4.00/src/bully.c:461:3:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
		fprintf(stderr, usage, argv[0], G->error);
data/bully-1.4.00/src/bully.c:491:2:  [4] (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).
	strcat(p_iface, G->ifname);
data/bully-1.4.00/src/bully.c:641:2:  [4] (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).
	strcat(p_bssid, G->ssids);
data/bully-1.4.00/src/bully.c:930: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(G->pinf, G->warpath);
data/bully-1.4.00/src/bully.c:932: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(G->pinf + wsize + 1, hex(G->bssid, 6));
data/bully-1.4.00/src/bully.c:939: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(G->runf, G->warpath);
data/bully-1.4.00/src/bully.c:941: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(G->runf + wsize + 1, hex(G->bssid, 6));
data/bully-1.4.00/src/bully.c:1015:12:  [4] (shell) popen:
  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.
			fpixe = popen(cmd_pixie, "r");
data/bully-1.4.00/src/bully.h:38:23:  [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	vprint(...) { snprintf(__vp,__vs,__VA_ARGS__); if ((__vp[1]=='+'?3:__vp[1]=='!'?2:1)<=__vb) fputs(__vp,__vf); }
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/luaclib.c:35:4:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
			printf(lua_toboolean(L, i) ? "true" : "false");
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/utils.c:306: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(oldf, G->warpath);
data/bully-1.4.00/src/utils.c:308:2:  [4] (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).
	strcat(oldf, G->ssids);
data/bully-1.4.00/src/utils/common.c:579:5:  [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(bssid_copy, mac);
data/bully-1.4.00/src/utils/common.c:586:13:  [4] (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).
            strcat(temp, bssid_parts);
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/utils/wpa_debug.c:112: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/bully-1.4.00/src/utils/wpa_debug.c:116: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/bully-1.4.00/src/utils/wpa_debug.c:331: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/bully-1.4.00/src/utils/wpa_debug.c:357: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/bully-1.4.00/src/utils/wpa_debug.c:389: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/bully-1.4.00/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/bully-1.4.00/src/wps/wps_attr_build.c:70:5:  [4] (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).
				strcat(pixie_pkr, get_pkr);
data/bully-1.4.00/src/wps/wps_common.c:132:4:  [4] (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).
			strcat(pixie_authkey, get_auth);
data/bully-1.4.00/src/wps/wps_registrar.c:1342:4:  [4] (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).
			strcat(pixie_rnonce, get_rnonce);
data/bully-1.4.00/src/wps/wps_registrar.c:1696:4:  [4] (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).
			strcat(pixie_enonce, get_enonce);
data/bully-1.4.00/src/wps/wps_registrar.c:1777:4:  [4] (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).
			strcat(pixie_ehash1, get_eh1);
data/bully-1.4.00/src/wps/wps_registrar.c:1814:4:  [4] (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).
			strcat(pixie_ehash2, get_eh2);
data/bully-1.4.00/src/wps/wps_registrar.c:1969:4:  [4] (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).
			strcat(pixie_pke, get_pke);
data/bully-1.4.00/src/wps/wps_upnp.c:323: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(mem, url);
data/bully-1.4.00/src/wps/wps_upnp.c:334: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(domain, domain_and_port);
data/bully-1.4.00/src/wps/wps_upnp.c:382: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(mem, domain_and_port);
data/bully-1.4.00/src/wps/wps_upnp.c:387: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(mem, path);
data/bully-1.4.00/src/bully.c:137:2:  [3] (random) srandom:
  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.
	srandom(time(NULL));
data/bully-1.4.00/src/bully.c:244:16:  [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.
		int option = getopt_long(argc, argv, "a:b:c:de:g:i:l:m:o:p:r:s:t:"
data/bully-1.4.00/src/bully.c:538:29:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
	if (-1 < G->pinstart && G->random) {
data/bully-1.4.00/src/bully.c:889:25:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
		wconf->wps->uuid[k] = random() % 255;
data/bully-1.4.00/src/bully.c:935:10:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
		if (G->random)
data/bully-1.4.00/src/bully.c:968:9:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
	if (G->random)
data/bully-1.4.00/src/bully.c:1164:11:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
			if (G->random)
data/bully-1.4.00/src/bully.h:160:6:  [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.
	int	random;
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/utils.c:174:17:  [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.
				while ((j = random() % 10000) == i);
data/bully-1.4.00/src/utils.c:183:17:  [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.
				while ((j = random() % 10000) == i);
data/bully-1.4.00/src/utils.c:357:9:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
	if (G->random) {
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/80211.c:106: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,pack,plen);
data/bully-1.4.00/src/80211.c:107: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[len-4],&buf[plen-4],4);
data/bully-1.4.00/src/80211.c:108: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[plen-4],msg,mlen);
data/bully-1.4.00/src/80211.c:154: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(oui, tag->data, 3);
data/bully-1.4.00/src/80211.c:161: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(oui, tag->data, 3);
data/bully-1.4.00/src/80211.c:198:10:  [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.
	case 0: strcpy(sbuf, "Default (PIN)");       break;
data/bully-1.4.00/src/80211.c:199:10:  [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.
	case 1: strcpy(sbuf, "User-specified");      break;
data/bully-1.4.00/src/80211.c:200:10:  [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.
	case 2: strcpy(sbuf, "Machine-specified");   break;
data/bully-1.4.00/src/80211.c:201:10:  [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.
	case 3: strcpy(sbuf, "Rekey");               break;
data/bully-1.4.00/src/80211.c:202:10:  [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.
	case 4: strcpy(sbuf, "PushButton");          break;
data/bully-1.4.00/src/80211.c:203:10:  [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.
	case 5: strcpy(sbuf, "Registrar-specified"); break;
data/bully-1.4.00/src/80211.c:216:3:  [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(sbuf, "Computer");
data/bully-1.4.00/src/80211.c:219:11:  [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.
		case 1: strcpy(sbuf, ", PC");                     break;
data/bully-1.4.00/src/80211.c:220:11:  [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.
		case 2: strcpy(sbuf, ", Server");                 break;
data/bully-1.4.00/src/80211.c:221:11:  [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.
		case 3: strcpy(sbuf, ", Media center");           break;
data/bully-1.4.00/src/80211.c:222:11:  [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.
		case 4: strcpy(sbuf, ", Ultra-mobile PC");        break;
data/bully-1.4.00/src/80211.c:223:11:  [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.
		case 5: strcpy(sbuf, ", Notebook");               break;
data/bully-1.4.00/src/80211.c:224:11:  [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.
		case 6: strcpy(sbuf, ", Desktop");                break;
data/bully-1.4.00/src/80211.c:225:11:  [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.
		case 7: strcpy(sbuf, ", Mobile Internet Device"); break;
data/bully-1.4.00/src/80211.c:226:11:  [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.
		case 8: strcpy(sbuf, ", Netbook");                break;
data/bully-1.4.00/src/80211.c:227:11:  [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.
		case 9: strcpy(sbuf, ", Tablet");                 break;
data/bully-1.4.00/src/80211.c:232:3:  [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(sbuf, "Input Device");
data/bully-1.4.00/src/80211.c:235:11:  [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.
		case 1: strcpy(sbuf, ", Keyboard");          break;
data/bully-1.4.00/src/80211.c:236:11:  [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.
		case 2: strcpy(sbuf, ", Mouse");             break;
data/bully-1.4.00/src/80211.c:237:11:  [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.
		case 3: strcpy(sbuf, ", Joystick");          break;
data/bully-1.4.00/src/80211.c:238:11:  [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.
		case 4: strcpy(sbuf, ", Trackball");         break;
data/bully-1.4.00/src/80211.c:239:11:  [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.
		case 5: strcpy(sbuf, ", Gaming controller"); break;
data/bully-1.4.00/src/80211.c:240:11:  [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.
		case 6: strcpy(sbuf, ", Remote");            break;
data/bully-1.4.00/src/80211.c:241:11:  [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.
		case 7: strcpy(sbuf, ", Touchscreen");       break;
data/bully-1.4.00/src/80211.c:242:11:  [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.
		case 8: strcpy(sbuf, ", Biometric reader");  break;
data/bully-1.4.00/src/80211.c:243:11:  [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.
		case 9: strcpy(sbuf, ", Barcode reader");    break;
data/bully-1.4.00/src/80211.c:248:3:  [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(sbuf, "Printer/Scanner");
data/bully-1.4.00/src/80211.c:251:11:  [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.
		case 1: strcpy(sbuf, ", Printer");    break;
data/bully-1.4.00/src/80211.c:252:11:  [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.
		case 2: strcpy(sbuf, ", Scanner");    break;
data/bully-1.4.00/src/80211.c:253:11:  [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.
		case 3: strcpy(sbuf, ", Fax");        break;
data/bully-1.4.00/src/80211.c:254:11:  [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.
		case 4: strcpy(sbuf, ", Copier");     break;
data/bully-1.4.00/src/80211.c:255:11:  [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.
		case 5: strcpy(sbuf, ", All-in-one"); break;
data/bully-1.4.00/src/80211.c:260:3:  [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(sbuf, "Camera");
data/bully-1.4.00/src/80211.c:263:11:  [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.
		case 1: strcpy(sbuf, ", Printer");    break;
data/bully-1.4.00/src/80211.c:264:11:  [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.
		case 2: strcpy(sbuf, ", Scanner");    break;
data/bully-1.4.00/src/80211.c:265:11:  [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.
		case 3: strcpy(sbuf, ", Fax");        break;
data/bully-1.4.00/src/80211.c:266:11:  [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.
		case 4: strcpy(sbuf, ", Copier");     break;
data/bully-1.4.00/src/80211.c:267:11:  [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.
		case 5: strcpy(sbuf, ", All-in-one"); break;
data/bully-1.4.00/src/80211.c:272:3:  [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(sbuf, "Storage");
data/bully-1.4.00/src/80211.c:275:11:  [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.
		case 1: strcpy(sbuf, ", NAS"); break;
data/bully-1.4.00/src/80211.c:280:3:  [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(sbuf, "Network Infrastructure");
data/bully-1.4.00/src/80211.c:283:11:  [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.
		case 1: strcpy(sbuf, ", AP");      break;
data/bully-1.4.00/src/80211.c:284:11:  [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.
		case 2: strcpy(sbuf, ", Router");  break;
data/bully-1.4.00/src/80211.c:285:11:  [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.
		case 3: strcpy(sbuf, ", Switch");  break;
data/bully-1.4.00/src/80211.c:286:11:  [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.
		case 4: strcpy(sbuf, ", Gateway"); break;
data/bully-1.4.00/src/80211.c:291:3:  [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(sbuf, "Display");
data/bully-1.4.00/src/80211.c:294:11:  [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.
		case 1: strcpy(sbuf, ", Television");               break;
data/bully-1.4.00/src/80211.c:295:11:  [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.
		case 2: strcpy(sbuf, ", Electronic Picture Frame"); break;
data/bully-1.4.00/src/80211.c:296:11:  [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.
		case 3: strcpy(sbuf, ", Projector");                break;
data/bully-1.4.00/src/80211.c:297:11:  [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.
		case 4: strcpy(sbuf, ", Monitor");                  break;
data/bully-1.4.00/src/80211.c:302:3:  [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(sbuf, "Multimedia Device");
data/bully-1.4.00/src/80211.c:305:11:  [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.
		case 1: strcpy(sbuf, ", DAR");                           break;
data/bully-1.4.00/src/80211.c:306:11:  [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.
		case 2: strcpy(sbuf, ", PVR");                           break;
data/bully-1.4.00/src/80211.c:307:11:  [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.
		case 3: strcpy(sbuf, ", MCX");                           break;
data/bully-1.4.00/src/80211.c:308:11:  [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.
		case 4: strcpy(sbuf, ", Set-top box");                   break;
data/bully-1.4.00/src/80211.c:309:11:  [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.
		case 5: strcpy(sbuf, ", Media server/adapter/extender"); break;
data/bully-1.4.00/src/80211.c:314:3:  [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(sbuf, "Gaming Device");
data/bully-1.4.00/src/80211.c:317:11:  [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.
		case 1: strcpy(sbuf, ", Xbox");                   break;
data/bully-1.4.00/src/80211.c:318:11:  [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.
		case 2: strcpy(sbuf, ", Xbox360");                break;
data/bully-1.4.00/src/80211.c:319:11:  [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.
		case 3: strcpy(sbuf, ", Playstation");            break;
data/bully-1.4.00/src/80211.c:320:11:  [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.
		case 4: strcpy(sbuf, ", Game console/adapter");   break;
data/bully-1.4.00/src/80211.c:321:11:  [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.
		case 5: strcpy(sbuf, ", Portable gaming device"); break;
data/bully-1.4.00/src/80211.c:326:3:  [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(sbuf, "Telephone");
data/bully-1.4.00/src/80211.c:329:11:  [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.
		case 1: strcpy(sbuf, ", Windows Mobile");           break;
data/bully-1.4.00/src/80211.c:330:11:  [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.
		case 2: strcpy(sbuf, ", Phone - single mode");      break;
data/bully-1.4.00/src/80211.c:331:11:  [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.
		case 3: strcpy(sbuf, ", Phone - dual mode");        break;
data/bully-1.4.00/src/80211.c:332:11:  [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.
		case 4: strcpy(sbuf, ", Smartphone - single mode"); break;
data/bully-1.4.00/src/80211.c:333:11:  [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.
		case 5: strcpy(sbuf, ", Smartphone - dual mode");   break;
data/bully-1.4.00/src/80211.c:338:3:  [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(sbuf, "Audio Device");
data/bully-1.4.00/src/80211.c:341:11:  [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.
		case 1: strcpy(sbuf, ", Audio tuner/receiver");  break;
data/bully-1.4.00/src/80211.c:342:11:  [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.
		case 2: strcpy(sbuf, ", Speakers");              break;
data/bully-1.4.00/src/80211.c:343:11:  [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.
		case 3: strcpy(sbuf, ", Portable Music Player"); break;
data/bully-1.4.00/src/80211.c:344:11:  [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.
		case 4: strcpy(sbuf, ", Headset");               break;
data/bully-1.4.00/src/80211.c:345:11:  [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.
		case 5: strcpy(sbuf, ", Headphones");            break;
data/bully-1.4.00/src/80211.c:346:11:  [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.
		case 6: strcpy(sbuf, ", Microphone");            break;
data/bully-1.4.00/src/80211.c:347:11:  [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.
		case 7: strcpy(sbuf, ", Home Threater Systems"); break;
data/bully-1.4.00/src/80211.c:363:3:  [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(sbuf, "Label");
data/bully-1.4.00/src/80211.c:368:4:  [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(sbuf + offset, ", ");
data/bully-1.4.00/src/80211.c:371:3:  [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(sbuf + offset, "Display");
data/bully-1.4.00/src/80211.c:376:4:  [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(sbuf + offset, ", ");
data/bully-1.4.00/src/80211.c:379:3:  [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(sbuf + offset, "Push Button");
data/bully-1.4.00/src/80211.c:384:4:  [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(sbuf + offset, ", ");
data/bully-1.4.00/src/80211.c:387:3:  [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(sbuf + offset, "Keypad");
data/bully-1.4.00/src/80211.c:392:4:  [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(sbuf + offset, ", ");
data/bully-1.4.00/src/80211.c:395:3:  [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(sbuf + offset, "Ethernet");
data/bully-1.4.00/src/80211.c:400:4:  [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(sbuf + offset, ", ");
data/bully-1.4.00/src/80211.c:403:3:  [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(sbuf + offset, "USB");
data/bully-1.4.00/src/80211.c:421: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(buf,*tags,(*tags)->len + sizeof(tag_t));
data/bully-1.4.00/src/bully.c:117: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	essids[33] = {0}, *essid = essids;
data/bully-1.4.00/src/bully.c:118: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	bssids[18] = {0};
data/bully-1.4.00/src/bully.c:119: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	hwmacs[18] = {0};
data/bully-1.4.00/src/bully.c:186:3:  [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(G->warpath, "/.");
data/bully-1.4.00/src/bully.c:301:15:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
				if ((of = fopen(optarg, "w")) != NULL)
data/bully-1.4.00/src/bully.c:564: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->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:567: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(tags[0]->data, G->essid, tags[0]->len);
data/bully-1.4.00/src/bully.c:599:8:  [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, G->essid, tag->len);
data/bully-1.4.00/src/bully.c:603: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(essids,tag->data,tag->len);
data/bully-1.4.00/src/bully.c:638: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(G->bssid, ((mac_t*)G->inp[F_MAC].data)->adr3.addr, 6);
data/bully-1.4.00/src/bully.c:648: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:649: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:650: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:653: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:654: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:655: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:658: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:659: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:660: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:663: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:664: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:665: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:668: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:669: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:670: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:673: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:674: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:675: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:678: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:681: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(mac->adr1.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:682: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(mac->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:683: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(mac->adr3.addr, G->bssid, 6);
data/bully-1.4.00/src/bully.c:707: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 vendor[OUI_STR_LEN];
data/bully-1.4.00/src/bully.c:708: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(vendor, get_vendor(wps_info.vendor), OUI_STR_LEN);
data/bully-1.4.00/src/bully.c:751: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->adr2.addr, G->hwmac, 6);
data/bully-1.4.00/src/bully.c:754: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(tags[0]->data, G->essid, tags[0]->len);
data/bully-1.4.00/src/bully.c:797: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 c_pwid[20];
data/bully-1.4.00/src/bully.c:806:6:  [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 c_buff[60];
data/bully-1.4.00/src/bully.c:814:6:  [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 c_buff[60];
data/bully-1.4.00/src/bully.c:821: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(wps_info.uuid, vtag->data, 16);
data/bully-1.4.00/src/bully.c:825: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(wps_info.device_name, vtag->data, tag_size);
data/bully-1.4.00/src/bully.c:831: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(wps_info.manufacturer, vtag->data, tag_size);
data/bully-1.4.00/src/bully.c:837: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(wps_info.model_name, vtag->data, tag_size);
data/bully-1.4.00/src/bully.c:843: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(wps_info.model_number, vtag->data, tag_size);
data/bully-1.4.00/src/bully.c:849: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(wps_info.serial_number, vtag->data, tag_size);
data/bully-1.4.00/src/bully.c:902: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(G->wdata->wps->dev.pri_dev_type, W7_DEVICE_TYPE, 8);
data/bully-1.4.00/src/bully.c:903: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(&G->wdata->wps->dev.os_version, W7_OS_VERSION, 4);
data/bully-1.4.00/src/bully.c:933:3:  [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(G->pinf + wsize + 1 + 12, ".pins");
data/bully-1.4.00/src/bully.c:942:3:  [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(G->runf + wsize + 1 + 12, ".run");
data/bully-1.4.00/src/bully.c:945: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	pinstr[9];
data/bully-1.4.00/src/bully.c:997: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(cmd_pixie,"pixiewps -e ");
data/bully-1.4.00/src/bully.c:999:4:  [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(cmd_pixie," -r ");
data/bully-1.4.00/src/bully.c:1001:4:  [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(cmd_pixie," -s ");
data/bully-1.4.00/src/bully.c:1003:4:  [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(cmd_pixie," -z ");
data/bully-1.4.00/src/bully.c:1005:4:  [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(cmd_pixie," -a ");
data/bully-1.4.00/src/bully.c:1007:4:  [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(cmd_pixie," -n ");
data/bully-1.4.00/src/bully.c:1009:4:  [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(cmd_pixie," -m ");
data/bully-1.4.00/src/bully.c:1011:4:  [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(cmd_pixie," -v 1 --force");
data/bully-1.4.00/src/bully.c:1121:16:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
					if ((rf = fopen(G->runf, "a")) != NULL) {
data/bully-1.4.00/src/bully.c:1189: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).
	if ((rf = fopen(G->runf, "a")) != NULL) {
data/bully-1.4.00/src/bully.h:40: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 hx[16] = "0123456789abcdef";
data/bully-1.4.00/src/bully.h:42: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 _xbuf[HEXSZ];
data/bully-1.4.00/src/bully.h:145: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	schan[8];
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/iface.c:77: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(G->schan, "unknown", 8);
data/bully-1.4.00/src/iface.c:101: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(mac, irq.ifr_hwaddr.sa_data, 6);
data/bully-1.4.00/src/pdust.c:24: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 OUI_NULL[OUI_STR_LEN] = "-";
data/bully-1.4.00/src/pdust.h:35: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[OUI_STR_LEN];
data/bully-1.4.00/src/pdust.h:40:8:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
extern char OUI_NULL[OUI_STR_LEN];
data/bully-1.4.00/src/pdust.h:55: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 manufacturer[64 + 1];
data/bully-1.4.00/src/pdust.h: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 device_name[32 + 1];
data/bully-1.4.00/src/pdust.h: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 model_name[32 + 1];
data/bully-1.4.00/src/pdust.h: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 model_number[32 + 1];
data/bully-1.4.00/src/pdust.h:59: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 serial_number[32 + 1];
data/bully-1.4.00/src/pingen.c:80: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[2] = { 0 };
data/bully-1.4.00/src/pixie.h:2: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 pixie_pke[1000];					/* save pke */
data/bully-1.4.00/src/pixie.h:3: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 pixie_pkr[1000];					/* save pkr */
data/bully-1.4.00/src/pixie.h:4: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 pixie_enonce[100];					/* save e-nonce */
data/bully-1.4.00/src/pixie.h:5: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 pixie_rnonce[100];					/* save r-nonce */
data/bully-1.4.00/src/pixie.h:6: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 pixie_authkey[100];				/* save AuthKey */
data/bully-1.4.00/src/pixie.h:7: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 pixie_ehash1[100];					/* save e-hash1 */
data/bully-1.4.00/src/pixie.h:8: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 pixie_ehash2[100];					/* save e-hash2 */
data/bully-1.4.00/src/pixie.h:10: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 p_iface[20];
data/bully-1.4.00/src/pixie.h:11: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 p_bssid[256];
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/utils.c:160: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).
	if ((pf = fopen(G->pinf, "r")) == 0) {
data/bully-1.4.00/src/utils.c:161: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 ((pf = fopen(G->pinf, "w")) == 0) {
data/bully-1.4.00/src/utils.c:309: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(oldf, ".run");
data/bully-1.4.00/src/utils.c:312: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).
	if ((rf = fopen(oldf, "r")) != NULL)
data/bully-1.4.00/src/utils.c:316: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).
	if ((rf = fopen(G->runf, "r")) == NULL) {
data/bully-1.4.00/src/utils.c:318: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 ((rf = fopen(G->runf, "w")) != NULL) {
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/utils/common.c:408: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[2] = { 0 };
data/bully-1.4.00/src/utils/common.c:473: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 buff_mac[24];
data/bully-1.4.00/src/utils/common.c:483: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(buff_mac,"%X",buff_mac_i);
data/bully-1.4.00/src/utils/common.c:549: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 buff[10];
data/bully-1.4.00/src/utils/common.c:577: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 *bssid_parts, temp[7] = { 0 };
data/bully-1.4.00/src/utils/common.c:608: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 mac_address[7] = {0};
data/bully-1.4.00/src/utils/common.c:610: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(mac_address, "%c%c%c%c%c%c", mac[6], mac[7], mac[8], mac[9], mac[10], mac[11]);
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/utils/wpa_debug.c:281: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/bully-1.4.00/src/wps/http_client.c:230: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).
		dst->sin_port = htons(atoi(port));
data/bully-1.4.00/src/wps/httpread.c:80: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 hdr[HTTPREAD_HEADER_MAX_SIZE+1];   /* headers stored here */
data/bully-1.4.00/src/wps/httpread.c:205:23:  [2] (integer) atol:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
		h->content_length = atol(hbp);
data/bully-1.4.00/src/wps/httpread.c:252:19:  [2] (integer) atol:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
		h->reply_code = atol(hbp);
data/bully-1.4.00/src/wps/httpread.c:408: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 readbuf[HTTPREAD_READBUF_SIZE];  /* temp use to read into */
data/bully-1.4.00/src/wps/pixie.h:2: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 pixie_pke[1000];					/* save pke */
data/bully-1.4.00/src/wps/pixie.h:3: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 pixie_pkr[1000];					/* save pkr */
data/bully-1.4.00/src/wps/pixie.h:4: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 pixie_enonce[100];					/* save e-nonce */
data/bully-1.4.00/src/wps/pixie.h:5: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 pixie_rnonce[100];					/* save r-nonce */
data/bully-1.4.00/src/wps/pixie.h:6: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 pixie_authkey[100];				/* save AuthKey */
data/bully-1.4.00/src/wps/pixie.h:7: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 pixie_ehash1[100];					/* save e-hash1 */
data/bully-1.4.00/src/wps/pixie.h:8: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 pixie_ehash2[100];					/* save e-hash2 */
data/bully-1.4.00/src/wps/pixie.h:10: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 p_iface[20];
data/bully-1.4.00/src/wps/pixie.h:11: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 p_bssid[256];
data/bully-1.4.00/src/wps/wps.c:457: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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/wps/wps_attr_build.c:69: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(get_pkr, "%02x",  v[pixiecnt]);
data/bully-1.4.00/src/wps/wps_common.c:131: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(get_auth, "%02x",  wps->authkey[pixiecnt]);
data/bully-1.4.00/src/wps/wps_common.c:557: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/bully-1.4.00/src/wps/wps_common.c:562: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/bully-1.4.00/src/wps/wps_common.c:573: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/bully-1.4.00/src/wps/wps_common.c:580: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/bully-1.4.00/src/wps/wps_dev_attr.c:406: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/bully-1.4.00/src/wps/wps_er.c:227: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 sid[100];
data/bully-1.4.00/src/wps/wps_er.c:313: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 txt[100];
data/bully-1.4.00/src/wps/wps_er.c:858: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 len_buf[10];
data/bully-1.4.00/src/wps/wps_er.c:1099:14:  [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).
		event_id = atoi(uri + 7);
data/bully-1.4.00/src/wps/wps_er.c:1109:30:  [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).
		wps_er_http_event(er, req, atoi(pos));
data/bully-1.4.00/src/wps/wps_er.h:78: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 ifname[17];
data/bully-1.4.00/src/wps/wps_er_ssdp.c:32: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[MULTICAST_MAX_READ], *pos, *pos2, *start;
data/bully-1.4.00/src/wps/wps_er_ssdp.c:91:14:  [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).
			max_age = atoi(pos2);
data/bully-1.4.00/src/wps/wps_registrar.c:1257: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/bully-1.4.00/src/wps/wps_registrar.c:1267: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/bully-1.4.00/src/wps/wps_registrar.c:1341: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(get_rnonce, "%02x", wps->nonce_r[pixiecnt]);
data/bully-1.4.00/src/wps/wps_registrar.c:1695: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(get_enonce, "%02x",  wps->nonce_e[pixiecnt]);
data/bully-1.4.00/src/wps/wps_registrar.c:1776: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(get_eh1, "%02x", wps->peer_hash1[pixiecnt]);
data/bully-1.4.00/src/wps/wps_registrar.c:1813: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(get_eh2, "%02x",  wps->peer_hash2[pixiecnt]);
data/bully-1.4.00/src/wps/wps_registrar.c:1968: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(get_pke, "%02x", pk[pixiecnt]);
data/bully-1.4.00/src/wps/wps_registrar.c:2989: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/bully-1.4.00/src/wps/wps_registrar.c:2990: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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/wps/wps_upnp.c:339:11:  [2] (integer) atol:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
			port = atol(delim);
data/bully-1.4.00/src/wps/wps_upnp.c:607: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 txt[10];
data/bully-1.4.00/src/wps/wps_upnp.c:751: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 type[2];
data/bully-1.4.00/src/wps/wps_upnp.c:753: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_text[18];
data/bully-1.4.00/src/wps/wps_upnp.c:805:26:  [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 int eth_get(const char *device, u8 ea[ETH_ALEN])
data/bully-1.4.00/src/wps/wps_upnp.c:852:26:  [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 get_netif_info(const char *net_if, unsigned *ip_addr, char **ip_addr_text,
data/bully-1.4.00/src/wps/wps_upnp.c:852:59:  [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 get_netif_info(const char *net_if, unsigned *ip_addr, char **ip_addr_text,
data/bully-1.4.00/src/wps/wps_upnp_i.h:148:26:  [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 get_netif_info(const char *net_if, unsigned *ip_addr, char **ip_addr_text,
data/bully-1.4.00/src/wps/wps_upnp_i.h:148:59:  [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 get_netif_info(const char *net_if, unsigned *ip_addr, char **ip_addr_text,
data/bully-1.4.00/src/wps/wps_upnp_ssdp.c:138: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_string[80];
data/bully-1.4.00/src/wps/wps_upnp_ssdp.c:590: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 uuid_string[80];
data/bully-1.4.00/src/wps/wps_upnp_ssdp.c:638:9:  [2] (integer) atol:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
			mx = atol(data);
data/bully-1.4.00/src/wps/wps_upnp_ssdp.c:697: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[MULTICAST_MAX_READ], *pos;
data/bully-1.4.00/src/wps/wps_upnp_web.c:186: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_string[80];
data/bully-1.4.00/src/wps/wps_upnp_web.c:313: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 len_buf[10];
data/bully-1.4.00/src/wps/wps_upnp_web.c:514:12:  [2] (integer) atol:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
	ev_type = atol(val);
data/bully-1.4.00/src/wps/wps_upnp_web.c:737: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 len_buf[10];
data/bully-1.4.00/src/bully.c:184:23:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
		G->warpath = malloc(strlen(temp) + strlen(EXE_NAME) + 3);
data/bully-1.4.00/src/bully.c:184: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).
		G->warpath = malloc(strlen(temp) + strlen(EXE_NAME) + 3);
data/bully-1.4.00/src/bully.c:335:31:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
				const unsigned int luap = strlen(optarg);
data/bully-1.4.00/src/bully.c:566: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).
		tags[0]->len = strlen(G->essid);
data/bully-1.4.00/src/bully.c:592: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).
				if (strlen(G->essid) != tag->len)
data/bully-1.4.00/src/bully.c:753: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).
		tags[0]->len = strlen(G->essid);
data/bully-1.4.00/src/bully.c:773: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).
				if (strlen(G->essid) != tag->len)
data/bully-1.4.00/src/bully.c:928: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 wsize = strlen(G->warpath);
data/bully-1.4.00/src/bully.c:998:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_pke, 1000);
data/bully-1.4.00/src/bully.c:1000:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_pkr, 1000);
data/bully-1.4.00/src/bully.c:1002:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_ehash1,100);
data/bully-1.4.00/src/bully.c:1004:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_ehash2,100);
data/bully-1.4.00/src/bully.c:1006:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_authkey,100);
data/bully-1.4.00/src/bully.c:1008:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_enonce,100);
data/bully-1.4.00/src/bully.c:1010:4:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct maximum
  size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
  or automatically resizing strings.
			strncat(cmd_pixie,pixie_rnonce,100);
data/bully-1.4.00/src/bully.c:1043: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).
					for(i=0;i<strlen(aux_pixie_pin);i++)
data/bully-1.4.00/src/bully.c:1047:8:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
							strncpy(pinstr, aux_pixie_pin + i, 8);
data/bully-1.4.00/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/bully-1.4.00/src/iface.c:38:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(wrq.ifr_name, G->ifname, IFNAMSIZ);
data/bully-1.4.00/src/iface.c:50:4:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
			usleep(10000);
data/bully-1.4.00/src/iface.c:96:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(irq.ifr_name, ifname, IFNAMSIZ);
data/bully-1.4.00/src/pingen.c:91: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).
  int serial_len = strlen(serial);
data/bully-1.4.00/src/utils.c:39: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).
	int i, o=0, len = strlen(in);
data/bully-1.4.00/src/utils.c:54: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).
	int i, o, k, len = strlen(in);
data/bully-1.4.00/src/utils.c:267:13:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			if ((t = fgetc(pf)) != EOF)
data/bully-1.4.00/src/utils.c:276:13:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			if ((t = fgetc(pf)) != EOF)
data/bully-1.4.00/src/utils.c:280:7:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		if (fgetc(pf) != EOF)
data/bully-1.4.00/src/utils.c:305: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).
	char *oldf = malloc(strlen(G->warpath) + 23);
data/bully-1.4.00/src/utils.c:307:2:  [1] (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 character.
	strcat(oldf, "/");
data/bully-1.4.00/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/bully-1.4.00/src/utils/common.c:476:15:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
    mac_len = strlen(mac);
data/bully-1.4.00/src/utils/common.c:485: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).
	mac_len = strlen(buff_mac);
data/bully-1.4.00/src/utils/common.c:551:20:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
    nic = hexToInt(strncpy(buff, mac+6, sizeof(buff)));
data/bully-1.4.00/src/utils/common.c:576: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).
    char *bssid_copy = (char *)malloc(strlen(mac) + 1);
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/wps/httpread.c:416:10:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	nread = read(h->sd, readbuf, sizeof(readbuf));
data/bully-1.4.00/src/wps/wps_attr_build.c:72:6:  [1] (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 character.
					strcat(pixie_pkr,":");
data/bully-1.4.00/src/wps/wps_common.c:134:4:  [1] (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 character.
			strcat(pixie_authkey,":");
data/bully-1.4.00/src/wps/wps_registrar.c:1344:5:  [1] (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 character.
				strcat(pixie_rnonce,":");
data/bully-1.4.00/src/wps/wps_registrar.c:1698:5:  [1] (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 character.
				strcat(pixie_enonce,":");
data/bully-1.4.00/src/wps/wps_registrar.c:1779:5:  [1] (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 character.
				strcat(pixie_ehash1,":");
data/bully-1.4.00/src/wps/wps_registrar.c:1816:5:  [1] (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 character.
				strcat(pixie_ehash2,":");
data/bully-1.4.00/src/wps/wps_registrar.c:1971:5:  [1] (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 character.
				strcat(pixie_pke,":");
data/bully-1.4.00/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/bully-1.4.00/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/bully-1.4.00/src/wps/wps_upnp.c:383:14:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
		mem += 1 + strlen(mem);
data/bully-1.4.00/src/wps/wps_upnp.c:388:14:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
		mem += 1 + strlen(mem);
data/bully-1.4.00/src/wps/wps_upnp_ssdp.c:724: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).
	    !isgraph(buf[strlen("M-SEARCH")])) {

ANALYSIS SUMMARY:

Hits = 553
Lines analyzed = 64779 in approximately 1.60 seconds (40363 lines/second)
Physical Source Lines of Code (SLOC) = 44954
Hits@level = [0] 159 [1]  56 [2] 338 [3]  19 [4] 139 [5]   1
Hits@level+ = [0+] 712 [1+] 553 [2+] 497 [3+] 159 [4+] 140 [5+]   1
Hits/KSLOC@level+ = [0+] 15.8384 [1+] 12.3015 [2+] 11.0557 [3+] 3.53695 [4+] 3.11429 [5+] 0.022245
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.