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/rpma-0.9.0/examples/01-connection/client.c
Examining data/rpma-0.9.0/examples/01-connection/server.c
Examining data/rpma-0.9.0/examples/02-read-to-volatile/client.c
Examining data/rpma-0.9.0/examples/02-read-to-volatile/server.c
Examining data/rpma-0.9.0/examples/03-read-to-persistent/client.c
Examining data/rpma-0.9.0/examples/03-read-to-persistent/server.c
Examining data/rpma-0.9.0/examples/04-write-to-persistent/client.c
Examining data/rpma-0.9.0/examples/04-write-to-persistent/server.c
Examining data/rpma-0.9.0/examples/05-flush-to-persistent/client.c
Examining data/rpma-0.9.0/examples/05-flush-to-persistent/server.c
Examining data/rpma-0.9.0/examples/06-multiple-connections/client.c
Examining data/rpma-0.9.0/examples/06-multiple-connections/multiple-connections-common.h
Examining data/rpma-0.9.0/examples/06-multiple-connections/server.c
Examining data/rpma-0.9.0/examples/07-atomic-write/client.c
Examining data/rpma-0.9.0/examples/07-atomic-write/server.c
Examining data/rpma-0.9.0/examples/08-messages-ping-pong/client.c
Examining data/rpma-0.9.0/examples/08-messages-ping-pong/messages-ping-pong-common.h
Examining data/rpma-0.9.0/examples/08-messages-ping-pong/server.c
Examining data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/GPSPM_flush.pb-c.c
Examining data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/GPSPM_flush.pb-c.h
Examining data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/client.c
Examining data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/flush-to-persistent-GPSPM.h
Examining data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/server.c
Examining data/rpma-0.9.0/examples/common/common-conn.c
Examining data/rpma-0.9.0/examples/common/common-conn.h
Examining data/rpma-0.9.0/examples/common/common-epoll.c
Examining data/rpma-0.9.0/examples/common/common-epoll.h
Examining data/rpma-0.9.0/examples/doc_snippets/template-snippet.c
Examining data/rpma-0.9.0/examples/log/log-example.c
Examining data/rpma-0.9.0/examples/log/log-worker.c
Examining data/rpma-0.9.0/examples/template-example/template-example.c
Examining data/rpma-0.9.0/src/cmocka_alloc.h
Examining data/rpma-0.9.0/src/common.h
Examining data/rpma-0.9.0/src/conn.c
Examining data/rpma-0.9.0/src/conn.h
Examining data/rpma-0.9.0/src/conn_cfg.c
Examining data/rpma-0.9.0/src/conn_cfg.h
Examining data/rpma-0.9.0/src/conn_req.c
Examining data/rpma-0.9.0/src/conn_req.h
Examining data/rpma-0.9.0/src/ep.c
Examining data/rpma-0.9.0/src/flush.c
Examining data/rpma-0.9.0/src/flush.h
Examining data/rpma-0.9.0/src/include/librpma.h
Examining data/rpma-0.9.0/src/info.c
Examining data/rpma-0.9.0/src/info.h
Examining data/rpma-0.9.0/src/librpma.c
Examining data/rpma-0.9.0/src/log.c
Examining data/rpma-0.9.0/src/log_default.c
Examining data/rpma-0.9.0/src/log_default.h
Examining data/rpma-0.9.0/src/log_internal.h
Examining data/rpma-0.9.0/src/mr.c
Examining data/rpma-0.9.0/src/mr.h
Examining data/rpma-0.9.0/src/peer.c
Examining data/rpma-0.9.0/src/peer.h
Examining data/rpma-0.9.0/src/peer_cfg.c
Examining data/rpma-0.9.0/src/peer_cfg.h
Examining data/rpma-0.9.0/src/private_data.c
Examining data/rpma-0.9.0/src/private_data.h
Examining data/rpma-0.9.0/src/rpma.c
Examining data/rpma-0.9.0/src/rpma_err.c
Examining data/rpma-0.9.0/src/valgrind/valgrind_internal.h
Examining data/rpma-0.9.0/tests/cmocka_headers.h
Examining data/rpma-0.9.0/tests/integration/common/mocks.c
Examining data/rpma-0.9.0/tests/integration/common/mocks.h
Examining data/rpma-0.9.0/tests/integration/example-01-connection/example-01-connection.c
Examining data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c
Examining data/rpma-0.9.0/tests/test_backtrace.c
Examining data/rpma-0.9.0/tests/test_backtrace.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-getpid.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-getpid.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-rdma_cm.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rdma_cm.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-conn.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-conn_cfg.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-conn_cfg.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-flush.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-flush.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-info.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-log.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-log_default.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-mr.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer_cfg.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-private_data.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-utils.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-rpma-utils.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-stdio.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-stdio.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-stdlib.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-stdlib.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-syslog.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-time.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-time.h
Examining data/rpma-0.9.0/tests/unit/common/mocks-unistd.c
Examining data/rpma-0.9.0/tests/unit/common/mocks-unistd.h
Examining data/rpma-0.9.0/tests/unit/common/test-common.h
Examining data/rpma-0.9.0/tests/unit/conn/conn-apply_remote_peer_cfg.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-common.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-common.h
Examining data/rpma-0.9.0/tests/unit/conn/conn-completion_get.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-completion_wait.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-disconnect.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-flush.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-get_completion_fd.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-get_event_fd.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-new.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-next_event.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-private_data.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-read.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-recv.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-send.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-write.c
Examining data/rpma-0.9.0/tests/unit/conn/conn-write_atomic.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-common.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-common.h
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-cq_size.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-cqe.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-delete.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-new.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-rq_size.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-sq_size.c
Examining data/rpma-0.9.0/tests/unit/conn_cfg/conn_cfg-timeout.c
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-common.c
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-common.h
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-connect.c
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-delete.c
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-from_cm_event.c
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-new.c
Examining data/rpma-0.9.0/tests/unit/conn_req/conn_req-recv.c
Examining data/rpma-0.9.0/tests/unit/ep/ep-common.c
Examining data/rpma-0.9.0/tests/unit/ep/ep-common.h
Examining data/rpma-0.9.0/tests/unit/ep/ep-get_fd.c
Examining data/rpma-0.9.0/tests/unit/ep/ep-listen.c
Examining data/rpma-0.9.0/tests/unit/ep/ep-next_conn_req.c
Examining data/rpma-0.9.0/tests/unit/error/error.c
Examining data/rpma-0.9.0/tests/unit/flush/flush-apm_do.c
Examining data/rpma-0.9.0/tests/unit/flush/flush-common.c
Examining data/rpma-0.9.0/tests/unit/flush/flush-common.h
Examining data/rpma-0.9.0/tests/unit/flush/flush-new.c
Examining data/rpma-0.9.0/tests/unit/info/info-bind_addr.c
Examining data/rpma-0.9.0/tests/unit/info/info-common.c
Examining data/rpma-0.9.0/tests/unit/info/info-common.h
Examining data/rpma-0.9.0/tests/unit/info/info-new.c
Examining data/rpma-0.9.0/tests/unit/info/info-resolve_addr.c
Examining data/rpma-0.9.0/tests/unit/librpma_constructor/librpma_constructor.c
Examining data/rpma-0.9.0/tests/unit/log/init-fini.c
Examining data/rpma-0.9.0/tests/unit/log/macros.c
Examining data/rpma-0.9.0/tests/unit/log/threshold.c
Examining data/rpma-0.9.0/tests/unit/log_default/function.c
Examining data/rpma-0.9.0/tests/unit/log_default/init-fini.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-common.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-common.h
Examining data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-get_flush_type.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-read.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-recv.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-reg.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-send.c
Examining data/rpma-0.9.0/tests/unit/mr/mr-write.c
Examining data/rpma-0.9.0/tests/unit/peer/peer-common.c
Examining data/rpma-0.9.0/tests/unit/peer/peer-common.h
Examining data/rpma-0.9.0/tests/unit/peer/peer-create_qp.c
Examining data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c
Examining data/rpma-0.9.0/tests/unit/peer/peer-new.c
Examining data/rpma-0.9.0/tests/unit/peer_cfg/peer_cfg-common.c
Examining data/rpma-0.9.0/tests/unit/peer_cfg/peer_cfg-common.h
Examining data/rpma-0.9.0/tests/unit/peer_cfg/peer_cfg-delete.c
Examining data/rpma-0.9.0/tests/unit/peer_cfg/peer_cfg-descriptor.c
Examining data/rpma-0.9.0/tests/unit/peer_cfg/peer_cfg-direct_write_to_pmem.c
Examining data/rpma-0.9.0/tests/unit/peer_cfg/peer_cfg-new.c
Examining data/rpma-0.9.0/tests/unit/private_data/private_data-common.c
Examining data/rpma-0.9.0/tests/unit/private_data/private_data-common.h
Examining data/rpma-0.9.0/tests/unit/private_data/private_data-copy.c
Examining data/rpma-0.9.0/tests/unit/private_data/private_data-store.c
Examining data/rpma-0.9.0/tests/unit/template/template.c
Examining data/rpma-0.9.0/tests/unit/utils/utils-common.c
Examining data/rpma-0.9.0/tests/unit/utils/utils-conn_event_2str.c
Examining data/rpma-0.9.0/tests/unit/utils/utils-get_ibv_context.c
Examining data/rpma-0.9.0/tests/unit/utils/utils-ibv_context_is_odp_capable.c
FINAL RESULTS:
data/rpma-0.9.0/examples/03-read-to-persistent/client.c:58: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_STR, argv[0]);
data/rpma-0.9.0/examples/03-read-to-persistent/server.c:29: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_STR, argv[0]);
data/rpma-0.9.0/examples/04-write-to-persistent/client.c:58: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_STR, argv[0]);
data/rpma-0.9.0/examples/04-write-to-persistent/server.c:29: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_STR, argv[0]);
data/rpma-0.9.0/examples/05-flush-to-persistent/client.c:61: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_STR, argv[0]);
data/rpma-0.9.0/examples/05-flush-to-persistent/server.c:34: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_STR, argv[0]);
data/rpma-0.9.0/examples/06-multiple-connections/client.c:45: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_STR, argv[0]);
data/rpma-0.9.0/examples/06-multiple-connections/server.c:388: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_STR, argv[0]);
data/rpma-0.9.0/examples/07-atomic-write/client.c:27: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_STR, argv[0]);
data/rpma-0.9.0/examples/07-atomic-write/client.c:148: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(word, argv[i]);
data/rpma-0.9.0/examples/07-atomic-write/server.c:44: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_STR, argv[0]);
data/rpma-0.9.0/examples/08-messages-ping-pong/client.c:40: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_STR, argv[0]);
data/rpma-0.9.0/examples/08-messages-ping-pong/server.c:27: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_STR, argv[0]);
data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/client.c:65: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_STR, argv[0]);
data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/server.c:33: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_STR, argv[0]);
data/rpma-0.9.0/examples/log/log-example.c:37:6: [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.
if (vfprintf(stderr, message_format, args) < 0) {
data/rpma-0.9.0/src/log_default.c:100:6: [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.
if (vsnprintf(message, sizeof(message), message_format, arg) < 0) {
data/rpma-0.9.0/src/mr.c:72:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access |= IBV_ACCESS_REMOTE_READ;
data/rpma-0.9.0/src/mr.c:79:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access |= IBV_ACCESS_LOCAL_WRITE;
data/rpma-0.9.0/src/mr.c:84:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access |= IBV_ACCESS_LOCAL_WRITE;
data/rpma-0.9.0/src/mr.c:93:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access |= IBV_ACCESS_REMOTE_WRITE | IBV_ACCESS_LOCAL_WRITE;
data/rpma-0.9.0/src/mr.c:98:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access |= IBV_ACCESS_LOCAL_WRITE;
data/rpma-0.9.0/src/mr.c:102:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/rpma-0.9.0/src/peer.c:101:25: [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.
#define RPMA_IBV_ACCESS(access) (unsigned)access
data/rpma-0.9.0/src/peer.c:101:43: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
#define RPMA_IBV_ACCESS(access) (unsigned)access
data/rpma-0.9.0/src/peer.c:103:25: [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.
#define RPMA_IBV_ACCESS(access) access
data/rpma-0.9.0/src/peer.c:103:33: [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.
#define RPMA_IBV_ACCESS(access) access
data/rpma-0.9.0/src/peer.c:111:34: [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.
void *addr, size_t length, int access)
data/rpma-0.9.0/src/peer.c:114:22: [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.
RPMA_IBV_ACCESS(access));
data/rpma-0.9.0/src/peer.c:128:18: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
addr, length, access);
data/rpma-0.9.0/src/peer.c:138:20: [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.
RPMA_IBV_ACCESS(access | IBV_ACCESS_ON_DEMAND));
data/rpma-0.9.0/src/peer.c:143:18: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
addr, length, access);
data/rpma-0.9.0/src/peer.h:36:34: [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.
void *addr, size_t length, int access);
data/rpma-0.9.0/tests/integration/common/mocks.c:515: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.
uint64_t iova, unsigned access)
data/rpma-0.9.0/tests/integration/common/mocks.c:517:43: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return ibv_reg_mr(pd, addr, length, (int)access);
data/rpma-0.9.0/tests/integration/common/mocks.c:526:62: [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.
ibv_reg_mr(struct ibv_pd *pd, void *addr, size_t length, int access)
data/rpma-0.9.0/tests/integration/common/mocks.c:530:17: [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.
check_expected(access);
data/rpma-0.9.0/tests/integration/example-01-connection/example-01-connection.c:100:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, IBV_ACCESS_LOCAL_WRITE);
data/rpma-0.9.0/tests/integration/example-01-connection/example-01-connection.c:252:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, IBV_ACCESS_LOCAL_WRITE);
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:96:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, IBV_ACCESS_LOCAL_WRITE);
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:144:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, IBV_ACCESS_LOCAL_WRITE);
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:297:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, IBV_ACCESS_REMOTE_READ);
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:340:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, IBV_ACCESS_LOCAL_WRITE);
data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.c:149: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.
uint64_t iova, unsigned access)
data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.c:151:43: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return ibv_reg_mr(pd, addr, length, (int)access);
data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.c:159:62: [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.
ibv_reg_mr(struct ibv_pd *pd, void *addr, size_t length, int access)
data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.c:164:17: [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.
check_expected(access);
data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer.c:41:34: [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.
void *addr, size_t length, int access)
data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer.c:54:19: [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.
assert_int_equal(access, args->access);
data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer.c:54:33: [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.
assert_int_equal(access, args->access);
data/rpma-0.9.0/tests/unit/common/mocks-rpma-peer.h:18:6: [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.
int access;
data/rpma-0.9.0/tests/unit/common/mocks-syslog.c:36:1: [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(int priority, const char *format, ...)
data/rpma-0.9.0/tests/unit/log/macros.c:33:14: [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.
assert_true(vsnprintf(output, MOCK_OUTPUT, message_format, ap) > 0);
data/rpma-0.9.0/tests/unit/log_default/function.c:124:14: [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.
will_return(syslog, MOCK_VALIDATE);
data/rpma-0.9.0/tests/unit/log_default/function.c:125:15: [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.
expect_value(syslog, priority,
data/rpma-0.9.0/tests/unit/log_default/function.c:130: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(msg, rpma_log_level_names[MOCK_LOG_LEVEL]);
data/rpma-0.9.0/tests/unit/log_default/function.c:131: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(msg, MOCK_FILE_ERROR_STR MOCK_MESSAGE);
data/rpma-0.9.0/tests/unit/log_default/function.c:132:16: [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.
expect_string(syslog, syslog_output, msg);
data/rpma-0.9.0/tests/unit/log_default/function.c:147:14: [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.
will_return(syslog, MOCK_VALIDATE);
data/rpma-0.9.0/tests/unit/log_default/function.c:148:15: [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.
expect_value(syslog, priority,
data/rpma-0.9.0/tests/unit/log_default/function.c:153: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(msg, rpma_log_level_names[MOCK_LOG_LEVEL]);
data/rpma-0.9.0/tests/unit/log_default/function.c:154: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(msg, MOCK_MESSAGE);
data/rpma-0.9.0/tests/unit/log_default/function.c:155:16: [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.
expect_string(syslog, syslog_output, msg);
data/rpma-0.9.0/tests/unit/log_default/function.c:172:14: [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.
will_return(syslog, MOCK_VALIDATE);
data/rpma-0.9.0/tests/unit/log_default/function.c:173:15: [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.
expect_value(syslog, priority,
data/rpma-0.9.0/tests/unit/log_default/function.c:178: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(msg, rpma_log_level_names[MOCK_LOG_LEVEL]);
data/rpma-0.9.0/tests/unit/log_default/function.c:179: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(msg, MOCK_FILE_NAME ": " STR(MOCK_LINE_NUMBER) ": "
data/rpma-0.9.0/tests/unit/log_default/function.c:181:16: [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.
expect_string(syslog, syslog_output, msg);
data/rpma-0.9.0/tests/unit/log_default/function.c:243:14: [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.
will_return(syslog, MOCK_PASSTHROUGH);
data/rpma-0.9.0/tests/unit/log_default/function.c:249: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(msg, MOCK_TIME_STR_EXPECTED(config));
data/rpma-0.9.0/tests/unit/log_default/function.c:250: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(msg, MOCK_PID_AS_STR);
data/rpma-0.9.0/tests/unit/log_default/function.c:251: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(msg, rpma_log_level_names[MOCK_LOG_LEVEL]);
data/rpma-0.9.0/tests/unit/log_default/function.c:252: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(msg, MOCK_FILE_NAME ": " STR(MOCK_LINE_NUMBER) ": "
data/rpma-0.9.0/tests/unit/log_default/function.c:282:15: [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.
will_return(syslog, MOCK_PASSTHROUGH);
data/rpma-0.9.0/tests/unit/log_default/function.c:288: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(msg, MOCK_TIME_STR_EXPECTED(config));
data/rpma-0.9.0/tests/unit/log_default/function.c:289: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(msg, MOCK_PID_AS_STR);
data/rpma-0.9.0/tests/unit/log_default/function.c:290: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(msg, rpma_log_level_names[MOCK_LOG_LEVEL]);
data/rpma-0.9.0/tests/unit/log_default/function.c:291: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(msg, MOCK_MESSAGE);
data/rpma-0.9.0/tests/unit/mr/mr-common.c:90:33: [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.
mr_reg_args.access = prestate->access;
data/rpma-0.9.0/tests/unit/mr/mr-common.h:55:6: [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.
int access;
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:33:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS);
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:59:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS);
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:86:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS);
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:94:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS | IBV_ACCESS_ON_DEMAND);
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:121:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS);
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:146:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS);
data/rpma-0.9.0/tests/unit/peer/peer-mr_reg.c:154:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
expect_value(ibv_reg_mr, access, MOCK_ACCESS | IBV_ACCESS_ON_DEMAND);
data/rpma-0.9.0/examples/06-multiple-connections/client.c:87:2: [3] (random) srand:
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.
srand(seed % UINT_MAX);
data/rpma-0.9.0/examples/02-read-to-volatile/server.c:75: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(mr_ptr, HELLO_STR, mr_size);
data/rpma-0.9.0/examples/03-read-to-persistent/client.c:34: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 str[KILOBYTE];
data/rpma-0.9.0/examples/03-read-to-persistent/client.c:133: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(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/03-read-to-persistent/server.c:101:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(dst_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/04-write-to-persistent/client.c:34: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 str[KILOBYTE];
data/rpma-0.9.0/examples/04-write-to-persistent/client.c:142: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(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/04-write-to-persistent/server.c:101: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(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/05-flush-to-persistent/client.c: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 str[KILOBYTE];
data/rpma-0.9.0/examples/05-flush-to-persistent/client.c:141: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(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/05-flush-to-persistent/server.c:107:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/06-multiple-connections/client.c:90: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 *)mr_ptr)[MAX_NAME_SIZE - 1] = '\0';
data/rpma-0.9.0/examples/07-atomic-write/server.c:33: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 signature[LOG_SIGNATURE_SIZE];
data/rpma-0.9.0/examples/07-atomic-write/server.c:36: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 data[LOG_DATA_SIZE];
data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/client.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 str[KILOBYTE];
data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/client.c:155: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(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/server.c:115: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(mr_ptr, SIGNATURE_STR, SIGNATURE_LEN);
data/rpma-0.9.0/examples/common/common-conn.h:33: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 descriptors[DESCRIPTORS_MAX_SIZE];
data/rpma-0.9.0/src/conn_cfg.c:92: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(*cfg_ptr, &Conn_cfg_default, sizeof(struct rpma_conn_cfg));
data/rpma-0.9.0/src/log_default.c:18: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.
static const char rpma_log_level_names[6][9] = {
data/rpma-0.9.0/src/log_default.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 date[24];
data/rpma-0.9.0/src/log_default.c:58: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, error_message, sizeof(error_message));
data/rpma-0.9.0/src/log_default.c:64: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, error_message, sizeof(error_message));
data/rpma-0.9.0/src/log_default.c:71: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, error_message, sizeof(error_message));
data/rpma-0.9.0/src/log_default.c:93:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char file_info_buffer[256] = "";
data/rpma-0.9.0/src/log_default.c:95: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 message[1024] = "";
data/rpma-0.9.0/src/log_default.c:127: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 times_tamp[45] = "";
data/rpma-0.9.0/src/mr.c:334: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(buff, &addr, sizeof(uint64_t));
data/rpma-0.9.0/src/mr.c:338: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(buff, &length, sizeof(uint64_t));
data/rpma-0.9.0/src/mr.c:342: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(buff, &rkey, sizeof(uint32_t));
data/rpma-0.9.0/src/mr.c:374: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(&raddr, buff, sizeof(uint64_t));
data/rpma-0.9.0/src/mr.c:377: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(&size, buff, sizeof(uint64_t));
data/rpma-0.9.0/src/mr.c:380: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(&rkey, buff, sizeof(uint32_t));
data/rpma-0.9.0/src/private_data.c:37: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(ptr_copy, ptr, len);
data/rpma-0.9.0/src/private_data.c:59: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(dst->ptr, src->ptr, src->len);
data/rpma-0.9.0/tests/integration/common/mocks.c:71: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(&attr->odp_caps, caps, sizeof(struct ibv_odp_caps));
data/rpma-0.9.0/tests/integration/common/mocks.c:147: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((void *)wr->sg_list->addr,
data/rpma-0.9.0/tests/integration/common/mocks.c:168: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(wc, wc_ret, sizeof(struct ibv_wc));
data/rpma-0.9.0/tests/integration/common/mocks.h:44: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 descriptors[DESCRIPTORS_MAX_SIZE];
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:39:2: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buff, &addr, sizeof(uint64_t));
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:43: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(buff, &length, sizeof(uint64_t));
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:47: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(buff, &key, sizeof(uint32_t));
data/rpma-0.9.0/tests/test_backtrace.c:53: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 procname[PROCNAMELEN];
data/rpma-0.9.0/tests/unit/common/mocks-ibverbs.c:60: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(&attr->odp_caps, caps, sizeof(struct ibv_odp_caps));
data/rpma-0.9.0/tests/unit/common/mocks-stdio.c:59: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 fprintf_output[MOCK_BUFF_LEN];
data/rpma-0.9.0/tests/unit/common/mocks-syslog.c:38:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char syslog_output[MOCK_BUFF_LEN];
data/rpma-0.9.0/tests/unit/common/mocks-time.c:26: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(__tp, tp, sizeof(struct timespec));
data/rpma-0.9.0/tests/unit/conn/conn-completion_get.c:32: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(wc, wc_ret, sizeof(struct ibv_wc));
data/rpma-0.9.0/tests/unit/log/macros.c:24: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 output[MOCK_OUTPUT];
data/rpma-0.9.0/tests/unit/log_default/function.c:54: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.
static char const rpma_log_level_names[6][9] = {
data/rpma-0.9.0/tests/unit/log_default/function.c:129: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 msg[MOCK_BUFF_LEN] = "";
data/rpma-0.9.0/tests/unit/log_default/function.c:152: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 msg[MOCK_BUFF_LEN] = "";
data/rpma-0.9.0/tests/unit/log_default/function.c:177: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 msg[MOCK_BUFF_LEN] = "";
data/rpma-0.9.0/tests/unit/log_default/function.c:248: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 msg[MOCK_BUFF_LEN] = "";
data/rpma-0.9.0/tests/unit/log_default/function.c:287: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 msg[MOCK_BUFF_LEN] = "";
data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c:213: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 desc_invalid[MR_DESC_SIZE];
data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c:336: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 buff_base[MR_DESC_SIZE * 2];
data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c:337: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 pattern[MR_DESC_SIZE * 2];
data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c:373: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 buff_base[MR_DESC_SIZE * 2];
data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c:374: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 pattern[MR_DESC_SIZE * 2];
data/rpma-0.9.0/tests/unit/mr/mr-descriptor.c:397: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(desc, desc_src, MR_DESC_SIZE);
data/rpma-0.9.0/examples/01-connection/client.c:64: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).
pdata.len = (strlen(msg) + 1) * sizeof(char);
data/rpma-0.9.0/examples/01-connection/server.c:72: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).
pdata.len = (strlen(msg) + 1) * sizeof(char);
data/rpma-0.9.0/examples/02-read-to-volatile/server.c:67: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).
mr_size = strlen(HELLO_STR) + 1;
data/rpma-0.9.0/examples/03-read-to-persistent/client.c:41:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(hello->str, hello_str[hello->lang], KILOBYTE - 1);
data/rpma-0.9.0/examples/04-write-to-persistent/client.c:41:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(hello->str, hello_str[hello->lang], KILOBYTE - 1);
data/rpma-0.9.0/examples/05-flush-to-persistent/client.c:44:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(hello->str, hello_str[hello->lang], KILOBYTE - 1);
data/rpma-0.9.0/examples/06-multiple-connections/client.c:89:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
(void) strncpy((char *)mr_ptr, name, (MAX_NAME_SIZE - 1));
data/rpma-0.9.0/examples/07-atomic-write/client.c:149: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).
size_t word_size = strlen(word) + 1;
data/rpma-0.9.0/examples/07-atomic-write/server.c:119:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(mr_ptr, LOG_HDR_SIGNATURE, LOG_SIGNATURE_SIZE);
data/rpma-0.9.0/examples/08-messages-ping-pong/client.c:158:11: [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.
(void) usleep(sleep_usec);
data/rpma-0.9.0/examples/09-flush-to-persistent-GPSPM/client.c:48:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(hello->str, hello_str[hello->lang], KILOBYTE - 1);
data/rpma-0.9.0/examples/common/common-conn.h:18:24: [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 SIGNATURE_LEN (strlen(SIGNATURE_STR) + 1)
data/rpma-0.9.0/tests/integration/example-01-connection/example-01-connection.c:112:41: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
f_event.param.conn.private_data_len = (strlen(msg) + 1) * sizeof(char);
data/rpma-0.9.0/tests/integration/example-01-connection/example-01-connection.c:217:41: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
f_event.param.conn.private_data_len = (strlen(msg) + 1) * sizeof(char);
data/rpma-0.9.0/tests/integration/example-01-connection/example-01-connection.c:262: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(s_msg) + 1) * sizeof(char);
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:18:24: [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 MOCK_READ_LEN (strlen(msg) + 1)
data/rpma-0.9.0/tests/integration/example-02-read-to-volatile/example-02-read-to-volatile.c:350: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(s_msg) + 1) * sizeof(char);
data/rpma-0.9.0/tests/test_backtrace.c:73:4: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
strcpy(procname, "?");
data/rpma-0.9.0/tests/unit/common/mocks-rpma-private_data.c:35: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).
pdata->len = strlen(pdata->ptr) + 1;
data/rpma-0.9.0/tests/unit/common/test-common.h:25:26: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
#define MOCK_PDATA_LEN (strlen(MOCK_PRIVATE_DATA) + 1)
data/rpma-0.9.0/tests/unit/common/test-common.h:27:27: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
#define MOCK_PDATA_LEN_2 (strlen(MOCK_PRIVATE_DATA_2) + 1)
data/rpma-0.9.0/tests/unit/conn/conn-common.c:68: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).
dst->len = strlen(dst->ptr) + 1;
data/rpma-0.9.0/tests/unit/private_data/private_data-common.h:26: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 DEFAULT_LEN (strlen(DEFAULT_VALUE) + 1)
ANALYSIS SUMMARY:
Hits = 171
Lines analyzed = 28993 in approximately 0.64 seconds (45342 lines/second)
Physical Source Lines of Code (SLOC) = 15815
Hits@level = [0] 135 [1] 23 [2] 60 [3] 1 [4] 87 [5] 0
Hits@level+ = [0+] 306 [1+] 171 [2+] 148 [3+] 88 [4+] 87 [5+] 0
Hits/KSLOC@level+ = [0+] 19.3487 [1+] 10.8125 [2+] 9.3582 [3+] 5.56434 [4+] 5.50111 [5+] 0
Dot directories skipped = 2 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.