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/websocketpp-0.8.2/docs/simple_broadcast_server.cpp
Examining data/websocketpp-0.8.2/docs/simple_count_server_thread.cpp
Examining data/websocketpp-0.8.2/examples/associative_storage/associative_storage.cpp
Examining data/websocketpp-0.8.2/examples/broadcast_server/broadcast_server.cpp
Examining data/websocketpp-0.8.2/examples/debug_client/debug_client.cpp
Examining data/websocketpp-0.8.2/examples/debug_server/debug_server.cpp
Examining data/websocketpp-0.8.2/examples/dev/main.cpp
Examining data/websocketpp-0.8.2/examples/echo_client/echo_client.cpp
Examining data/websocketpp-0.8.2/examples/echo_server/echo_handler.hpp
Examining data/websocketpp-0.8.2/examples/echo_server/echo_server.cpp
Examining data/websocketpp-0.8.2/examples/echo_server_both/echo_server_both.cpp
Examining data/websocketpp-0.8.2/examples/echo_server_tls/echo_server_tls.cpp
Examining data/websocketpp-0.8.2/examples/enriched_storage/enriched_storage.cpp
Examining data/websocketpp-0.8.2/examples/external_io_service/external_io_service.cpp
Examining data/websocketpp-0.8.2/examples/external_io_service/tcp_echo_server.hpp
Examining data/websocketpp-0.8.2/examples/handler_switch/handler_switch.cpp
Examining data/websocketpp-0.8.2/examples/iostream_server/iostream_server.cpp
Examining data/websocketpp-0.8.2/examples/print_client/print_client.cpp
Examining data/websocketpp-0.8.2/examples/print_client_tls/print_client_tls.cpp
Examining data/websocketpp-0.8.2/examples/print_server/print_server.cpp
Examining data/websocketpp-0.8.2/examples/scratch_client/scratch_client.cpp
Examining data/websocketpp-0.8.2/examples/scratch_server/scratch_server.cpp
Examining data/websocketpp-0.8.2/examples/simple_broadcast_server/simple_broadcast_server.cpp
Examining data/websocketpp-0.8.2/examples/sip_client/sip_client.cpp
Examining data/websocketpp-0.8.2/examples/subprotocol_server/subprotocol_server.cpp
Examining data/websocketpp-0.8.2/examples/telemetry_client/telemetry_client.cpp
Examining data/websocketpp-0.8.2/examples/telemetry_server/telemetry_server.cpp
Examining data/websocketpp-0.8.2/examples/testee_client/testee_client.cpp
Examining data/websocketpp-0.8.2/examples/testee_server/testee_server.cpp
Examining data/websocketpp-0.8.2/examples/utility_client/utility_client.cpp
Examining data/websocketpp-0.8.2/test/connection/connection.cpp
Examining data/websocketpp-0.8.2/test/connection/connection_tu2.cpp
Examining data/websocketpp-0.8.2/test/connection/connection_tu2.hpp
Examining data/websocketpp-0.8.2/test/endpoint/endpoint.cpp
Examining data/websocketpp-0.8.2/test/extension/extension.cpp
Examining data/websocketpp-0.8.2/test/extension/permessage_deflate.cpp
Examining data/websocketpp-0.8.2/test/http/parser.cpp
Examining data/websocketpp-0.8.2/test/http/parser_perf.cpp
Examining data/websocketpp-0.8.2/test/logger/basic.cpp
Examining data/websocketpp-0.8.2/test/message_buffer/alloc.cpp
Examining data/websocketpp-0.8.2/test/message_buffer/message.cpp
Examining data/websocketpp-0.8.2/test/message_buffer/pool.cpp
Examining data/websocketpp-0.8.2/test/processors/extension_permessage_compress.cpp
Examining data/websocketpp-0.8.2/test/processors/hybi00.cpp
Examining data/websocketpp-0.8.2/test/processors/hybi07.cpp
Examining data/websocketpp-0.8.2/test/processors/hybi08.cpp
Examining data/websocketpp-0.8.2/test/processors/hybi13.cpp
Examining data/websocketpp-0.8.2/test/processors/processor.cpp
Examining data/websocketpp-0.8.2/test/random/none.cpp
Examining data/websocketpp-0.8.2/test/random/random_device.cpp
Examining data/websocketpp-0.8.2/test/roles/client.cpp
Examining data/websocketpp-0.8.2/test/roles/server.cpp
Examining data/websocketpp-0.8.2/test/transport/asio/base.cpp
Examining data/websocketpp-0.8.2/test/transport/asio/security.cpp
Examining data/websocketpp-0.8.2/test/transport/asio/timers.cpp
Examining data/websocketpp-0.8.2/test/transport/hybi_util.cpp
Examining data/websocketpp-0.8.2/test/transport/integration.cpp
Examining data/websocketpp-0.8.2/test/transport/iostream/base.cpp
Examining data/websocketpp-0.8.2/test/transport/iostream/connection.cpp
Examining data/websocketpp-0.8.2/test/transport/iostream/endpoint.cpp
Examining data/websocketpp-0.8.2/test/utility/close.cpp
Examining data/websocketpp-0.8.2/test/utility/error.cpp
Examining data/websocketpp-0.8.2/test/utility/frame.cpp
Examining data/websocketpp-0.8.2/test/utility/sha1.cpp
Examining data/websocketpp-0.8.2/test/utility/uri.cpp
Examining data/websocketpp-0.8.2/test/utility/utilities.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_client/step1.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_client/step2.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_client/step3.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_client/step4.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_client/step5.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_client/step6.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_server/step1.cpp
Examining data/websocketpp-0.8.2/tutorials/utility_server/step2.cpp
Examining data/websocketpp-0.8.2/websocketpp/base64/base64.hpp
Examining data/websocketpp-0.8.2/websocketpp/client.hpp
Examining data/websocketpp-0.8.2/websocketpp/close.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/asio.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/asio_ssl.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/chrono.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/connection_hdl.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/cpp11.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/functional.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/md5.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/memory.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/network.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/platforms.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/random.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/regex.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/stdint.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/system_error.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/thread.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/time.hpp
Examining data/websocketpp-0.8.2/websocketpp/common/type_traits.hpp
Examining data/websocketpp-0.8.2/websocketpp/concurrency/basic.hpp
Examining data/websocketpp-0.8.2/websocketpp/concurrency/none.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/asio.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/asio_client.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/asio_no_tls.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/asio_no_tls_client.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/boost_config.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/core.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/core_client.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/debug.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/debug_asio.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/debug_asio_no_tls.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/minimal_client.hpp
Examining data/websocketpp-0.8.2/websocketpp/config/minimal_server.hpp
Examining data/websocketpp-0.8.2/websocketpp/connection.hpp
Examining data/websocketpp-0.8.2/websocketpp/connection_base.hpp
Examining data/websocketpp-0.8.2/websocketpp/endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/endpoint_base.hpp
Examining data/websocketpp-0.8.2/websocketpp/error.hpp
Examining data/websocketpp-0.8.2/websocketpp/extensions/extension.hpp
Examining data/websocketpp-0.8.2/websocketpp/extensions/permessage_deflate/disabled.hpp
Examining data/websocketpp-0.8.2/websocketpp/extensions/permessage_deflate/enabled.hpp
Examining data/websocketpp-0.8.2/websocketpp/frame.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/constants.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/impl/parser.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/impl/request.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/impl/response.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/parser.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/request.hpp
Examining data/websocketpp-0.8.2/websocketpp/http/response.hpp
Examining data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp
Examining data/websocketpp-0.8.2/websocketpp/impl/endpoint_impl.hpp
Examining data/websocketpp-0.8.2/websocketpp/impl/utilities_impl.hpp
Examining data/websocketpp-0.8.2/websocketpp/logger/basic.hpp
Examining data/websocketpp-0.8.2/websocketpp/logger/levels.hpp
Examining data/websocketpp-0.8.2/websocketpp/logger/stub.hpp
Examining data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp
Examining data/websocketpp-0.8.2/websocketpp/message_buffer/alloc.hpp
Examining data/websocketpp-0.8.2/websocketpp/message_buffer/message.hpp
Examining data/websocketpp-0.8.2/websocketpp/message_buffer/pool.hpp
Examining data/websocketpp-0.8.2/websocketpp/processors/base.hpp
Examining data/websocketpp-0.8.2/websocketpp/processors/hybi00.hpp
Examining data/websocketpp-0.8.2/websocketpp/processors/hybi07.hpp
Examining data/websocketpp-0.8.2/websocketpp/processors/hybi08.hpp
Examining data/websocketpp-0.8.2/websocketpp/processors/hybi13.hpp
Examining data/websocketpp-0.8.2/websocketpp/processors/processor.hpp
Examining data/websocketpp-0.8.2/websocketpp/random/none.hpp
Examining data/websocketpp-0.8.2/websocketpp/random/random_device.hpp
Examining data/websocketpp-0.8.2/websocketpp/roles/client_endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/roles/server_endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/server.hpp
Examining data/websocketpp-0.8.2/websocketpp/sha1/sha1.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/asio/base.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/asio/connection.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/asio/endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/asio/security/base.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/asio/security/none.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/asio/security/tls.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/base/connection.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/base/endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/debug/base.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/debug/connection.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/debug/endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/iostream/base.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/iostream/connection.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/iostream/endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/stub/base.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/stub/connection.hpp
Examining data/websocketpp-0.8.2/websocketpp/transport/stub/endpoint.hpp
Examining data/websocketpp-0.8.2/websocketpp/uri.hpp
Examining data/websocketpp-0.8.2/websocketpp/utf8_validator.hpp
Examining data/websocketpp-0.8.2/websocketpp/utilities.hpp
Examining data/websocketpp-0.8.2/websocketpp/version.hpp
FINAL RESULTS:
data/websocketpp-0.8.2/test/transport/asio/timers.cpp:64:20: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
boost::system::error_code ec;
data/websocketpp-0.8.2/test/transport/asio/timers.cpp:75:21: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
} catch (boost::system::error_code & ec) {
data/websocketpp-0.8.2/test/transport/asio/timers.cpp:84:12: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
boost::system::error_code ec;
data/websocketpp-0.8.2/test/transport/integration.cpp:231:20: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
boost::system::error_code ec;
data/websocketpp-0.8.2/test/transport/integration.cpp:242:21: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
} catch (boost::system::error_code & ec) {
data/websocketpp-0.8.2/test/transport/integration.cpp:260:20: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
boost::system::error_code ec;
data/websocketpp-0.8.2/test/transport/integration.cpp:271:21: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
} catch (boost::system::error_code & ec) {
data/websocketpp-0.8.2/test/transport/integration.cpp:374:31: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
void expired(const boost::system::error_code & ec)
data/websocketpp-0.8.2/websocketpp/common/asio.hpp:132:22: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
using boost::system::error_code;
data/websocketpp-0.8.2/websocketpp/common/asio.hpp:133:33: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
namespace errc = boost::system::errc;
data/websocketpp-0.8.2/websocketpp/common/system_error.hpp:72:29: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
namespace errc = boost::system::errc;
data/websocketpp-0.8.2/websocketpp/common/system_error.hpp:73:18: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
using boost::system::error_code;
data/websocketpp-0.8.2/websocketpp/common/system_error.hpp:74:18: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
using boost::system::error_category;
data/websocketpp-0.8.2/websocketpp/common/system_error.hpp:75:18: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
using boost::system::error_condition;
data/websocketpp-0.8.2/websocketpp/common/system_error.hpp:76:18: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
using boost::system::system_error;
data/websocketpp-0.8.2/websocketpp/common/system_error.hpp:77:80: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
#define _WEBSOCKETPP_ERROR_CODE_ENUM_NS_START_ namespace boost { namespace system {
data/websocketpp-0.8.2/websocketpp/endpoint.hpp:92:74: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
: m_alog(new alog_type(config::alog_level, log::channel_type_hint::access))
data/websocketpp-0.8.2/websocketpp/logger/basic.hpp:62:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
channel_type_hint::access)
data/websocketpp-0.8.2/websocketpp/logger/basic.hpp:73:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
channel_type_hint::access)
data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp:46:7: [4] (format) syslog:
If syslog's format strings can be influenced by an attacker, they can be
exploited (CWE-134). Use a constant format string for syslog.
class syslog : public basic<concurrency, names> {
data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp:54:5: [4] (format) syslog:
If syslog's format strings can be influenced by an attacker, they can be
exploited (CWE-134). Use a constant format string for syslog.
syslog<concurrency,names>(channel_type_hint::value hint =
data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp:55:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
channel_type_hint::access)
data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp:63:5: [4] (format) syslog:
If syslog's format strings can be influenced by an attacker, they can be
exploited (CWE-134). Use a constant format string for syslog.
syslog<concurrency,names>(level channels, channel_type_hint::value hint =
data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp:64:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
channel_type_hint::access)
data/websocketpp-0.8.2/websocketpp/logger/syslog.hpp:100:55: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (m_channel_type_hint == channel_type_hint::access) {
data/websocketpp-0.8.2/test/connection/connection.cpp:101:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/test/processors/hybi07.cpp:51:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/test/processors/hybi08.cpp:51:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/test/processors/hybi13.cpp:54:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/test/processors/hybi13.cpp:76:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/test/random/none.cpp:35:18: [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.
websocketpp::random::none::int_generator<int32_t> rng;
data/websocketpp-0.8.2/test/random/random_device.cpp:38:18: [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.
websocketpp::random::random_device::int_generator<int32_t,websocketpp::concurrency::none> rng;
data/websocketpp-0.8.2/test/roles/client.cpp:54:26: [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.
typedef websocketpp::random::random_device::int_generator<uint32_t,concurrency_type> rng_type;
data/websocketpp-0.8.2/websocketpp/common/random.hpp:75:18: [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.
using boost::random::random_device;
data/websocketpp-0.8.2/websocketpp/common/random.hpp:76:18: [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.
using boost::random::uniform_int_distribution;
data/websocketpp-0.8.2/websocketpp/config/core.hpp:93:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/websocketpp/config/core_client.hpp:100:26: [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.
typedef websocketpp::random::random_device::int_generator<uint32_t,
data/websocketpp-0.8.2/websocketpp/config/debug.hpp:93:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/websocketpp/config/minimal_server.hpp:119:26: [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.
typedef websocketpp::random::none::int_generator<uint32_t> rng_type;
data/websocketpp-0.8.2/websocketpp/random/none.hpp:33: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.
namespace random {
data/websocketpp-0.8.2/websocketpp/random/random_device.hpp:34: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.
namespace random {
data/websocketpp-0.8.2/examples/external_io_service/tcp_echo_server.hpp:71: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 m_buffer[1024];
data/websocketpp-0.8.2/examples/iostream_server/iostream_server.cpp:48:13: [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).
log.open("output.log");
data/websocketpp-0.8.2/examples/scratch_client/scratch_client.cpp:256:22: [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).
int id = atoi(input.substr(5).c_str());
data/websocketpp-0.8.2/examples/telemetry_server/telemetry_server.cpp:129:14: [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).
file.open(filename.c_str(), std::ios::in);
data/websocketpp-0.8.2/examples/telemetry_server/telemetry_server.cpp:192:17: [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).
int i = atoi(argv[2]);
data/websocketpp-0.8.2/examples/testee_client/testee_client.cpp:89:22: [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).
case_count = atoi(msg->get_payload().c_str());
data/websocketpp-0.8.2/examples/testee_server/testee_server.cpp:103:16: [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).
port = atoi(argv[1]);
data/websocketpp-0.8.2/examples/testee_server/testee_server.cpp:104:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
num_threads = atoi(argv[2]);
data/websocketpp-0.8.2/examples/utility_client/utility_client.cpp:311:22: [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).
int id = atoi(input.substr(5).c_str());
data/websocketpp-0.8.2/test/connection/connection.cpp:332: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 frame0[10] = {char(0x82), char(0x83), 0x00, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01};
data/websocketpp-0.8.2/test/connection/connection.cpp:339: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 frame1[4] = {char(0x88), 0x19, 0x03, char(0xf1)};
data/websocketpp-0.8.2/test/processors/hybi00.cpp:227:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 raw_header[1] = {0x00};
data/websocketpp-0.8.2/test/processors/hybi00.cpp:228:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 raw_payload[4] = {0x66,0x6f,0x6f,0xff};
data/websocketpp-0.8.2/test/roles/server.cpp:173:17: [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).
std::string open;
data/websocketpp-0.8.2/test/roles/server.cpp:178:56: [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).
s.set_open_handler(bind(&open_func_subprotocol,&s,&open,::_1));
data/websocketpp-0.8.2/test/roles/server.cpp:182:23: [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).
BOOST_CHECK_EQUAL(open, "");
data/websocketpp-0.8.2/test/roles/server.cpp:191:17: [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).
std::string open;
data/websocketpp-0.8.2/test/roles/server.cpp:196:56: [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).
s.set_open_handler(bind(&open_func_subprotocol,&s,&open,::_1));
data/websocketpp-0.8.2/test/roles/server.cpp:200:23: [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).
BOOST_CHECK_EQUAL(open, "foo");
data/websocketpp-0.8.2/test/roles/server.cpp:209:17: [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).
std::string open;
data/websocketpp-0.8.2/test/roles/server.cpp:214:56: [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).
s.set_open_handler(bind(&open_func_subprotocol,&s,&open,::_1));
data/websocketpp-0.8.2/test/roles/server.cpp:227:17: [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).
std::string open;
data/websocketpp-0.8.2/test/roles/server.cpp:232:56: [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).
s.set_open_handler(bind(&open_func_subprotocol,&s,&open,::_1));
data/websocketpp-0.8.2/test/roles/server.cpp:236:23: [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).
BOOST_CHECK_EQUAL(open, "bar");
data/websocketpp-0.8.2/test/transport/asio/timers.cpp:63:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char data[512];
data/websocketpp-0.8.2/test/transport/integration.cpp:230:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char data[512];
data/websocketpp-0.8.2/test/transport/integration.cpp:259:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char data[512];
data/websocketpp-0.8.2/test/transport/integration.cpp:614:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[2] = { char(0x81), char(0x80) };
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:394: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:403: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:413: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:449: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:483: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:489: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 input[10] = "abcdefg";
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:507:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[20];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:515: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 input[11] = "aaaaabbbbb";
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:532:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[20];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:538: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 input[11] = "aaaaabbbbb";
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:547: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:556: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:598: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[10];
data/websocketpp-0.8.2/test/transport/iostream/connection.cpp:604: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 input[10] = "foo";
data/websocketpp-0.8.2/test/utility/sha1.cpp:40:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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[20];
data/websocketpp-0.8.2/test/utility/sha1.cpp:41:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 reference[20] = {0xa9, 0x99, 0x3e, 0x36, 0x47,
data/websocketpp-0.8.2/test/utility/sha1.cpp:52:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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[20];
data/websocketpp-0.8.2/test/utility/sha1.cpp:53:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 reference[20] = {0x84, 0x98, 0x3e, 0x44, 0x1c,
data/websocketpp-0.8.2/test/utility/sha1.cpp:66:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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[20];
data/websocketpp-0.8.2/test/utility/sha1.cpp:67:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 reference[20] = {0x34, 0xaa, 0x97, 0x3c, 0xd4,
data/websocketpp-0.8.2/tutorials/utility_client/step4.cpp:178:22: [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).
int id = atoi(input.substr(5).c_str());
data/websocketpp-0.8.2/tutorials/utility_client/step5.cpp:256:22: [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).
int id = atoi(input.substr(5).c_str());
data/websocketpp-0.8.2/tutorials/utility_client/step6.cpp:311:22: [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).
int id = atoi(input.substr(5).c_str());
data/websocketpp-0.8.2/websocketpp/base64/base64.hpp:70:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 char_array_3[3];
data/websocketpp-0.8.2/websocketpp/base64/base64.hpp:71:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 char_array_4[4];
data/websocketpp-0.8.2/websocketpp/base64/base64.hpp:136:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (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 char_array_4[4], char_array_3[3];
data/websocketpp-0.8.2/websocketpp/close.hpp:277: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 c[2];
data/websocketpp-0.8.2/websocketpp/common/md5.hpp:206:14: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(xbuf, data, 64);
data/websocketpp-0.8.2/websocketpp/common/md5.hpp:376:10: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(pms->buf + offset, p, copy);
data/websocketpp-0.8.2/websocketpp/common/md5.hpp:390:10: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(pms->buf, p, left);
data/websocketpp-0.8.2/websocketpp/common/md5.hpp:416: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 digest[16];
data/websocketpp-0.8.2/websocketpp/common/md5.hpp:431: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.
const char hexval[16] = {'0', '1', '2', '3', '4', '5', '6', '7', '8', '9', 'a', 'b', 'c', 'd', 'e', 'f'};
data/websocketpp-0.8.2/websocketpp/common/network.hpp:71:18: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char c[8];
data/websocketpp-0.8.2/websocketpp/common/time.hpp:44: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(&tm_snapshot, ::localtime(&time), sizeof(std::tm));
data/websocketpp-0.8.2/websocketpp/connection.hpp:1542: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 m_buf[config::connection_read_buffer_size];
data/websocketpp-0.8.2/websocketpp/extensions/permessage_deflate/enabled.hpp:704:32: [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).
uint8_t bits = uint8_t(atoi(value.c_str()));
data/websocketpp-0.8.2/websocketpp/extensions/permessage_deflate/enabled.hpp:760:32: [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).
uint8_t bits = uint8_t(atoi(value.c_str()));
data/websocketpp-0.8.2/websocketpp/http/impl/response.hpp:140: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[istream_buffer];
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:112:40: [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).
if (m_state != session::state::open) {
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:162:40: [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).
if (m_state != session::state::open) {
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:259:40: [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).
if (m_state != session::state::open) {
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:317:36: [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).
if (m_state != session::state::open) {
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:1094:48: [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).
if (m_state != session::state::open) {
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:1424:31: [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).
m_state = session::state::open;
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:1635:35: [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).
m_state = session::state::open;
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:1952:66: [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).
if (op != frame::opcode::CLOSE && m_state != session::state::open) {
data/websocketpp-0.8.2/websocketpp/impl/connection_impl.hpp:2020:40: [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).
if (m_state == session::state::open) {
data/websocketpp-0.8.2/websocketpp/logger/basic.hpp:185:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[20];
data/websocketpp-0.8.2/websocketpp/processors/hybi00.hpp:103:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char key_final[16];
data/websocketpp-0.8.2/websocketpp/processors/hybi13.hpp:262:18: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char raw_key[16];
data/websocketpp-0.8.2/websocketpp/processors/hybi13.hpp:736:18: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char message_digest[20];
data/websocketpp-0.8.2/websocketpp/transport/asio/endpoint.hpp:426:21: [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).
m_acceptor->open(ep.protocol(),bec);
data/websocketpp-0.8.2/websocketpp/uri.hpp:330:57: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
unsigned int t_port = static_cast<unsigned int>(atoi(port.c_str()));
data/websocketpp-0.8.2/examples/print_client_tls/print_client_tls.cpp:67:60: [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 (ASN1_STRING_length(current_name->d.dNSName) != strlen(dns_name)) {
data/websocketpp-0.8.2/examples/print_client_tls/print_client_tls.cpp:101:49: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (ASN1_STRING_length(common_name_asn1) != strlen(common_name_str)) {
data/websocketpp-0.8.2/test/utility/frame.cpp:175:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(h1_solution,h1_solution+12,h1.bytes) );
data/websocketpp-0.8.2/test/utility/frame.cpp:176:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(h2_solution,h2_solution+12,h2.bytes) );
data/websocketpp-0.8.2/test/utility/frame.cpp:177:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(h3_solution,h3_solution+12,h3.bytes) );
data/websocketpp-0.8.2/test/utility/frame.cpp:178:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(h4_solution,h4_solution+12,h4.bytes) );
data/websocketpp-0.8.2/test/utility/frame.cpp:179:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(h5_solution,h5_solution+12,h5.bytes) );
data/websocketpp-0.8.2/test/utility/frame.cpp:225:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(p1.begin(),p1.end(),reinterpret_cast<char*>(s1)) );
data/websocketpp-0.8.2/test/utility/frame.cpp:233:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(p2.begin(),p2.end(),reinterpret_cast<char*>(s2)) );
data/websocketpp-0.8.2/test/utility/frame.cpp:305:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+15,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:327:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+15,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:351:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+15,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:373:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+15,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:397:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:405:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+7,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:409:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:434:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:442:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+7,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:446:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(output,output+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:469:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:476:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+7,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:480:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:503:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:510:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+7,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:514:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+16,masked) );
data/websocketpp-0.8.2/test/utility/frame.cpp:537:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
BOOST_CHECK( std::equal(buffer,buffer+12,unmasked) );
data/websocketpp-0.8.2/websocketpp/http/impl/response.hpp:118:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read < len) {
data/websocketpp-0.8.2/websocketpp/http/impl/response.hpp:119:48: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read += this->process_body(buf+read,(len-read));
data/websocketpp-0.8.2/websocketpp/http/impl/response.hpp:119:58: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read += this->process_body(buf+read,(len-read));
data/websocketpp-0.8.2/websocketpp/http/impl/response.hpp:125:20: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return read;
data/websocketpp-0.8.2/websocketpp/transport/iostream/connection.hpp:146:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
t.read(in);
data/websocketpp-0.8.2/websocketpp/transport/iostream/connection.hpp:603:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
void read(std::istream &in) {
data/websocketpp-0.8.2/websocketpp/transport/iostream/connection.hpp:612:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
in.read(m_buf+m_cursor,static_cast<std::streamsize>(m_len-m_cursor));
data/websocketpp-0.8.2/websocketpp/uri.hpp:60:34: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (uri_len >= 7 && std::equal(it,it+6,"wss://")) {
data/websocketpp-0.8.2/websocketpp/uri.hpp:64:41: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
} else if (uri_len >= 6 && std::equal(it,it+5,"ws://")) {
data/websocketpp-0.8.2/websocketpp/uri.hpp:68:41: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
} else if (uri_len >= 8 && std::equal(it,it+7,"http://")) {
data/websocketpp-0.8.2/websocketpp/uri.hpp:72:41: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
} else if (uri_len >= 9 && std::equal(it,it+8,"https://")) {
ANALYSIS SUMMARY:
Hits = 159
Lines analyzed = 38123 in approximately 1.11 seconds (34298 lines/second)
Physical Source Lines of Code (SLOC) = 19572
Hits@level = [0] 1 [1] 37 [2] 81 [3] 16 [4] 25 [5] 0
Hits@level+ = [0+] 160 [1+] 159 [2+] 122 [3+] 41 [4+] 25 [5+] 0
Hits/KSLOC@level+ = [0+] 8.17494 [1+] 8.12385 [2+] 6.23339 [3+] 2.09483 [4+] 1.27733 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.