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/liburing-0.7/examples/io_uring-cp.c
Examining data/liburing-0.7/examples/io_uring-test.c
Examining data/liburing-0.7/examples/link-cp.c
Examining data/liburing-0.7/examples/ucontext-cp.c
Examining data/liburing-0.7/src/include/liburing.h
Examining data/liburing-0.7/src/include/liburing/barrier.h
Examining data/liburing-0.7/src/include/liburing/io_uring.h
Examining data/liburing-0.7/src/queue.c
Examining data/liburing-0.7/src/register.c
Examining data/liburing-0.7/src/setup.c
Examining data/liburing-0.7/src/syscall.c
Examining data/liburing-0.7/src/syscall.h
Examining data/liburing-0.7/test/232c93d07b74-test.c
Examining data/liburing-0.7/test/35fa71a030ca-test.c
Examining data/liburing-0.7/test/500f9fbadef8-test.c
Examining data/liburing-0.7/test/7ad0e4b2f83c-test.c
Examining data/liburing-0.7/test/8a9973408177-test.c
Examining data/liburing-0.7/test/917257daa0fe-test.c
Examining data/liburing-0.7/test/a0908ae19763-test.c
Examining data/liburing-0.7/test/a4c0b3decb33-test.c
Examining data/liburing-0.7/test/accept-link.c
Examining data/liburing-0.7/test/accept-reuse.c
Examining data/liburing-0.7/test/accept-test.c
Examining data/liburing-0.7/test/accept.c
Examining data/liburing-0.7/test/across-fork.c
Examining data/liburing-0.7/test/b19062a56726-test.c
Examining data/liburing-0.7/test/b5837bd5311d-test.c
Examining data/liburing-0.7/test/ce593a6c480a-test.c
Examining data/liburing-0.7/test/close-opath.c
Examining data/liburing-0.7/test/connect.c
Examining data/liburing-0.7/test/cq-full.c
Examining data/liburing-0.7/test/cq-overflow-peek.c
Examining data/liburing-0.7/test/cq-overflow.c
Examining data/liburing-0.7/test/cq-peek-batch.c
Examining data/liburing-0.7/test/cq-ready.c
Examining data/liburing-0.7/test/cq-size.c
Examining data/liburing-0.7/test/d4ae271dfaae-test.c
Examining data/liburing-0.7/test/d77a67ed5f27-test.c
Examining data/liburing-0.7/test/defer.c
Examining data/liburing-0.7/test/eeed8b54e0df-test.c
Examining data/liburing-0.7/test/eventfd-disable.c
Examining data/liburing-0.7/test/eventfd-ring.c
Examining data/liburing-0.7/test/eventfd.c
Examining data/liburing-0.7/test/fadvise.c
Examining data/liburing-0.7/test/fallocate.c
Examining data/liburing-0.7/test/fc2a85cb02ef-test.c
Examining data/liburing-0.7/test/file-register.c
Examining data/liburing-0.7/test/file-update.c
Examining data/liburing-0.7/test/fixed-link.c
Examining data/liburing-0.7/test/fsync.c
Examining data/liburing-0.7/test/io-cancel.c
Examining data/liburing-0.7/test/io_uring_enter.c
Examining data/liburing-0.7/test/io_uring_register.c
Examining data/liburing-0.7/test/io_uring_setup.c
Examining data/liburing-0.7/test/iopoll.c
Examining data/liburing-0.7/test/lfs-openat-write.c
Examining data/liburing-0.7/test/lfs-openat.c
Examining data/liburing-0.7/test/link-timeout.c
Examining data/liburing-0.7/test/link.c
Examining data/liburing-0.7/test/link_drain.c
Examining data/liburing-0.7/test/madvise.c
Examining data/liburing-0.7/test/nop.c
Examining data/liburing-0.7/test/open-close.c
Examining data/liburing-0.7/test/openat2.c
Examining data/liburing-0.7/test/personality.c
Examining data/liburing-0.7/test/poll-cancel-ton.c
Examining data/liburing-0.7/test/poll-cancel.c
Examining data/liburing-0.7/test/poll-link.c
Examining data/liburing-0.7/test/poll-many.c
Examining data/liburing-0.7/test/poll-v-poll.c
Examining data/liburing-0.7/test/poll.c
Examining data/liburing-0.7/test/probe.c
Examining data/liburing-0.7/test/read-write.c
Examining data/liburing-0.7/test/ring-leak.c
Examining data/liburing-0.7/test/send_recv.c
Examining data/liburing-0.7/test/send_recvmsg.c
Examining data/liburing-0.7/test/shared-wq.c
Examining data/liburing-0.7/test/short-read.c
Examining data/liburing-0.7/test/socket-rw.c
Examining data/liburing-0.7/test/splice.c
Examining data/liburing-0.7/test/sq-full-cpp.cc
Examining data/liburing-0.7/test/sq-full.c
Examining data/liburing-0.7/test/sq-poll-kthread.c
Examining data/liburing-0.7/test/sq-space_left.c
Examining data/liburing-0.7/test/statx.c
Examining data/liburing-0.7/test/stdout.c
Examining data/liburing-0.7/test/submit-reuse.c
Examining data/liburing-0.7/test/teardowns.c
Examining data/liburing-0.7/test/timeout-overflow.c
Examining data/liburing-0.7/test/timeout.c
FINAL RESULTS:
data/liburing-0.7/test/35fa71a030ca-test.c:117:3: [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.
vsnprintf(buf, sizeof(buf), what, args);
data/liburing-0.7/test/a4c0b3decb33-test.c:42:2: [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.
vsnprintf(buf, sizeof(buf), what, args);
data/liburing-0.7/test/fc2a85cb02ef-test.c:24:3: [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.
vsnprintf(buf, sizeof(buf), what, args);
data/liburing-0.7/test/lfs-openat-write.c:20: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, __VA_ARGS__);\
data/liburing-0.7/test/lfs-openat.c:17: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, __VA_ARGS__);\
data/liburing-0.7/test/sq-poll-kthread.c:138:6: [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.
if (system("ps --ppid 2 | grep " KTHREAD_NAME) == 0) {
data/liburing-0.7/test/poll-cancel-ton.c:57:21: [3] (random) lrand48:
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.
data = sqe_index[lrand48() % nr];
data/liburing-0.7/test/poll-link.c:209: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(getpid());
data/liburing-0.7/examples/io_uring-cp.c:238:9: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
infd = open(argv[1], O_RDONLY);
data/liburing-0.7/examples/io_uring-cp.c:243:10: [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).
outfd = open(argv[2], O_WRONLY | O_CREAT | O_TRUNC, 0644);
data/liburing-0.7/examples/io_uring-test.c:38:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(argv[1], O_RDONLY | O_DIRECT);
data/liburing-0.7/examples/link-cp.c:171:9: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
infd = open(argv[1], O_RDONLY);
data/liburing-0.7/examples/link-cp.c:176:10: [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).
outfd = open(argv[2], O_WRONLY | O_CREAT | O_TRUNC, 0644);
data/liburing-0.7/examples/ucontext-cp.c:31:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char stack_buf[SIGSTKSZ];
data/liburing-0.7/examples/ucontext-cp.c:211:10: [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).
infd = open(argv[i], O_RDONLY);
data/liburing-0.7/examples/ucontext-cp.c:216:11: [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).
outfd = open(argv[i + 1], O_WRONLY | O_CREAT | O_TRUNC, 0644);
data/liburing-0.7/test/232c93d07b74-test.c:85: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(addr.sun_path, "\0sock", 6);
data/liburing-0.7/test/232c93d07b74-test.c:114:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buff[RECV_BUFF_SIZE];
data/liburing-0.7/test/232c93d07b74-test.c:193: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(addr.sun_path, "\0sock", 6);
data/liburing-0.7/test/232c93d07b74-test.c:213:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buff[SEND_BUFF_SIZE];
data/liburing-0.7/test/35fa71a030ca-test.c:114:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/liburing-0.7/test/35fa71a030ca-test.c:121:12: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int fd = open(file, O_WRONLY | O_CLOEXEC);
data/liburing-0.7/test/35fa71a030ca-test.c:152:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char abort[300];
data/liburing-0.7/test/35fa71a030ca-test.c:155:16: [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).
int fd = open(abort, O_WRONLY);
data/liburing-0.7/test/500f9fbadef8-test.c:23:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/500f9fbadef8-test.c:44:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/8a9973408177-test.c:13:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/8a9973408177-test.c:16:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/8a9973408177-test.c:17:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(buf);
data/liburing-0.7/test/8a9973408177-test.c: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 buf[32];
data/liburing-0.7/test/8a9973408177-test.c:47:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/8a9973408177-test.c:48:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(buf);
data/liburing-0.7/test/a4c0b3decb33-test.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 buf[1024];
data/liburing-0.7/test/a4c0b3decb33-test.c:46:11: [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).
int fd = open(file, O_WRONLY | O_CLOEXEC);
data/liburing-0.7/test/a4c0b3decb33-test.c:77: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 abort[300];
data/liburing-0.7/test/a4c0b3decb33-test.c:80: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).
int fd = open(abort, O_WRONLY);
data/liburing-0.7/test/accept-test.c:38: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(addr.sun_path, "\0sock", 6);
data/liburing-0.7/test/accept.c:26:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[128];
data/liburing-0.7/test/across-fork.c:30:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/across-fork.c:34:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(buf, O_RDWR | O_CREAT | O_APPEND, S_IRUSR | S_IWUSR);
data/liburing-0.7/test/across-fork.c:90:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[512];
data/liburing-0.7/test/across-fork.c:116:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/ce593a6c480a-test.c:18:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[8] = {0, 0, 0, 0, 0, 0, 1};
data/liburing-0.7/test/ce593a6c480a-test.c:43:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[8] = {0, 0, 0, 0, 0, 0, 1};
data/liburing-0.7/test/cq-overflow.c:44:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/cq-overflow.c:65:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_RDONLY | O_DIRECT);
data/liburing-0.7/test/d4ae271dfaae-test.c:27:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/d4ae271dfaae-test.c:72:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(fname, O_RDONLY | O_DIRECT);
data/liburing-0.7/test/defer.c:69: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(&ctx->cqes[i], cqe, sizeof(*cqe));
data/liburing-0.7/test/eeed8b54e0df-test.c:27:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open("testfile", O_RDWR | O_CREAT, 0644);
data/liburing-0.7/test/fadvise.c:53:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/fadvise.c:135:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(filename, O_RDONLY);
data/liburing-0.7/test/fallocate.c:25:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/fallocate.c:39:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/fallocate.c:40:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(buf);
data/liburing-0.7/test/fallocate.c:87:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/fallocate.c:90:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/fallocate.c:91:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(buf);
data/liburing-0.7/test/fallocate.c:151:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/fallocate.c:157:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/fallocate.c:158:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(buf);
data/liburing-0.7/test/fc2a85cb02ef-test.c:21:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/liburing-0.7/test/fc2a85cb02ef-test.c:28:12: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int fd = open(file, O_WRONLY | O_CLOEXEC);
data/liburing-0.7/test/fc2a85cb02ef-test.c:44:8: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open("/proc/thread-self/fail-nth", O_RDWR);
data/liburing-0.7/test/fc2a85cb02ef-test.c:47:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[16];
data/liburing-0.7/test/fc2a85cb02ef-test.c:48:3: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "%d", nth + 1);
data/liburing-0.7/test/file-register.c:19: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 fname[32];
data/liburing-0.7/test/file-register.c:26:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".reg.%d", i);
data/liburing-0.7/test/file-register.c:28:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".add.%d", i + add);
data/liburing-0.7/test/file-register.c:37: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 fname[32];
data/liburing-0.7/test/file-register.c:45:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".reg.%d", i);
data/liburing-0.7/test/file-register.c:47:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".add.%d", i + add);
data/liburing-0.7/test/file-register.c:48: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).
files[i] = open(fname, O_RDWR | O_CREAT, 0644);
data/liburing-0.7/test/file-register.c:508:16: [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).
files[7193] = open(".reg.7193", O_RDWR | O_CREAT, 0644);
data/liburing-0.7/test/file-update.c:17: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 fname[32];
data/liburing-0.7/test/file-update.c:24:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".reg.%d", i);
data/liburing-0.7/test/file-update.c:26:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".add.%d", i + add);
data/liburing-0.7/test/file-update.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 fname[32];
data/liburing-0.7/test/file-update.c:43:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".reg.%d", i);
data/liburing-0.7/test/file-update.c:45:4: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(fname, ".add.%d", i + add);
data/liburing-0.7/test/file-update.c:46: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).
files[i] = open(fname, O_RDWR | O_CREAT, 0644);
data/liburing-0.7/test/fixed-link.c:24:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open("/dev/zero", O_RDONLY);
data/liburing-0.7/test/fsync.c:19:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[32];
data/liburing-0.7/test/fsync.c:22:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buf, "./XXXXXX");
data/liburing-0.7/test/fsync.c:23:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(buf);
data/liburing-0.7/test/fsync.c:65:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open("testfile", O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/fsync.c:149:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/fsync.c:170:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(".sync_file_range", O_RDWR);
data/liburing-0.7/test/io-cancel.c:45:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/io-cancel.c:189:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_RDWR | O_DIRECT);
data/liburing-0.7/test/io_uring_enter.c:100:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[4096];
data/liburing-0.7/test/io_uring_enter.c:102:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(template);
data/liburing-0.7/test/io_uring_enter.c:180: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 template[32] = "/tmp/io_uring_enter-test.XXXXXX";
data/liburing-0.7/test/io_uring_register.c:86: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 template[32] = "io_uring_register-test-XXXXXXXX";
data/liburing-0.7/test/io_uring_register.c:88:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(template);
data/liburing-0.7/test/io_uring_register.c:126: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 template[32] = "io_uring_register-test-XXXXXXXX";
data/liburing-0.7/test/io_uring_register.c:147:15: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fdtable_fd = mkstemp(template);
data/liburing-0.7/test/io_uring_register.c:159:10: [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).
io_fd = open("/dev/null", O_RDWR);
data/liburing-0.7/test/io_uring_register.c:506:12: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
devnull = open("/dev/null", O_RDWR);
data/liburing-0.7/test/io_uring_setup.c:23: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 flagstr[64];
data/liburing-0.7/test/io_uring_setup.c:46:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char flagstr[64];
data/liburing-0.7/test/io_uring_setup.c:86: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 resvstr[4096];
data/liburing-0.7/test/io_uring_setup.c:91:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(resvstr, "0x%.8x 0x%.8x 0x%.8x", p->resv[0],
data/liburing-0.7/test/io_uring_setup.c:176:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[4096];
data/liburing-0.7/test/iopoll.c:48:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/iopoll.c:111:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, open_flags);
data/liburing-0.7/test/lfs-openat-write.c:103:8: [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).
dfd = open("/tmp", O_RDONLY | O_DIRECTORY);
data/liburing-0.7/test/lfs-openat.c:81:12: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int dfd = open("/tmp", O_PATH);
data/liburing-0.7/test/link-timeout.c:306: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 buffer[128];
data/liburing-0.7/test/link-timeout.c:383: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 buffer[128];
data/liburing-0.7/test/link-timeout.c:471: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 buffer[128];
data/liburing-0.7/test/link-timeout.c:543: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 buffer[128];
data/liburing-0.7/test/link_drain.c:22: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[5] = {0};
data/liburing-0.7/test/link_drain.c:23: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 expect[5] = {0, 1, 2, 3, 4};
data/liburing-0.7/test/link_drain.c:25:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open("testfile", O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/link_drain.c:105: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[9] = {0};
data/liburing-0.7/test/link_drain.c:106: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 expect[9] = {0, 1, 2, 3, 4, 5, 6, 7, 8};
data/liburing-0.7/test/link_drain.c:108:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open("testfile", O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/madvise.c:55:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/madvise.c:109:2: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buf, ptr, FILE_SIZE);
data/liburing-0.7/test/madvise.c:120:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(filename, O_RDONLY);
data/liburing-0.7/test/open-close.c:24:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/openat2.c:24:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/personality.c:78:8: [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).
ret = open(FNAME, O_RDONLY | O_CREAT, 0600);
data/liburing-0.7/test/poll-v-poll.c:175:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(fname, O_RDONLY);
data/liburing-0.7/test/read-write.c:49:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/read-write.c:89:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, open_flags);
data/liburing-0.7/test/read-write.c:285:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY);
data/liburing-0.7/test/read-write.c:525:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY);
data/liburing-0.7/test/read-write.c:612:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(".efbig", O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/ring-leak.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 buf[CMSG_SPACE(sizeof(fd))];
data/liburing-0.7/test/send_recv.c:122:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[MAX_MSG + 1];
data/liburing-0.7/test/send_recvmsg.c:139:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[MAX_MSG + 1];
data/liburing-0.7/test/short-read.c:25:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/short-read.c:54:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(".short-read", O_RDONLY);
data/liburing-0.7/test/socket-rw.c:82: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 recv_buff[128];
data/liburing-0.7/test/socket-rw.c:83: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 send_buff[128];
data/liburing-0.7/test/splice.c:78:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(filename, O_RDWR | O_CREAT, 0644);
data/liburing-0.7/test/splice.c:109:11: [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).
rnd_fd = open("/dev/urandom", O_RDONLY);
data/liburing-0.7/test/statx.c:42:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/statx.c:105:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(path, O_RDONLY);
data/liburing-0.7/test/stdout.c:20:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[128];
data/liburing-0.7/test/stdout.c:27: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(vecs[0].iov_base, str, strlen(str));
data/liburing-0.7/test/stdout.c:111: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(vecs.iov_base, str, strlen(str));
data/liburing-0.7/test/submit-reuse.c:48:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(file, O_WRONLY | O_CREAT, 0644);
data/liburing-0.7/test/submit-reuse.c:59: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 str1[STR_SIZE];
data/liburing-0.7/test/submit-reuse.c:60: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 str2[STR_SIZE];
data/liburing-0.7/test/submit-reuse.c:156:8: [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).
fd1 = open(".reuse.1", O_RDONLY);
data/liburing-0.7/test/submit-reuse.c:157:8: [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).
fd2 = open(".reuse.2", O_RDONLY);
data/liburing-0.7/examples/io_uring-cp.c:24:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int read;
data/liburing-0.7/examples/io_uring-cp.c:72:12: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (data->read)
data/liburing-0.7/examples/io_uring-cp.c:211:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (data->read) {
data/liburing-0.7/test/232c93d07b74-test.c:253:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(100000);
data/liburing-0.7/test/35fa71a030ca-test.c:29:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(ms * 1000);
data/liburing-0.7/test/35fa71a030ca-test.c:53:7: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(50);
data/liburing-0.7/test/35fa71a030ca-test.c:120:13: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int len = strlen(buf);
data/liburing-0.7/test/35fa71a030ca-test.c:142:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(1000);
data/liburing-0.7/test/a4c0b3decb33-test.c:26:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(ms * 1000);
data/liburing-0.7/test/a4c0b3decb33-test.c:45: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).
int len = strlen(buf);
data/liburing-0.7/test/a4c0b3decb33-test.c:67:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(1000);
data/liburing-0.7/test/accept.c:244:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(usecs);
data/liburing-0.7/test/accept.c:287:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(usecs);
data/liburing-0.7/test/across-fork.c:57:18: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
iovec.iov_len = strlen(str);
data/liburing-0.7/test/across-fork.c:99:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read(fd, buf, sizeof(buf) - 1) < 0)
data/liburing-0.7/test/ce593a6c480a-test.c:111:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(loop_fd, buf, 8);
data/liburing-0.7/test/cq-overflow.c:111:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(usecs);
data/liburing-0.7/test/cq-overflow.c:265:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(2 * 10000);
data/liburing-0.7/test/cq-overflow.c:417:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(1100000);
data/liburing-0.7/test/d4ae271dfaae-test.c:101:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(1000);
data/liburing-0.7/test/d77a67ed5f27-test.c:42:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(150000);
data/liburing-0.7/test/fadvise.c:116:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(fd, buf, FILE_SIZE);
data/liburing-0.7/test/fc2a85cb02ef-test.c:27:13: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int len = strlen(buf);
data/liburing-0.7/test/fc2a85cb02ef-test.c:49:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (write(fd, buf, strlen(buf)) != (ssize_t)strlen(buf))
data/liburing-0.7/test/fc2a85cb02ef-test.c:49:47: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (write(fd, buf, strlen(buf)) != (ssize_t)strlen(buf))
data/liburing-0.7/test/fixed-link.c:51:23: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
iovecs[i].iov_len = strlen(str);
data/liburing-0.7/test/fixed-link.c:52:57: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
io_uring_prep_read_fixed(sqe, fd, iovecs[i].iov_base, strlen(str), 0, i);
data/liburing-0.7/test/io-cancel.c:211:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(usecs / 3);
data/liburing-0.7/test/io_uring_enter.c:113:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(fd, buf, 4096);
data/liburing-0.7/test/io_uring_setup.c:34:3: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is low because the source is a
constant string.
strncat(flagstr, "IORING_FEAT_SINGLE_MMAP", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:34:52: [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).
strncat(flagstr, "IORING_FEAT_SINGLE_MMAP", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:64:3: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is low because the source is a
constant string.
strncat(flagstr, "IORING_SETUP_IOPOLL", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:64:48: [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).
strncat(flagstr, "IORING_SETUP_IOPOLL", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:69:4: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is low because the source is a
constant character.
strncat(flagstr, "|", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:69:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
strncat(flagstr, "|", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:72:3: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is low because the source is a
constant string.
strncat(flagstr, "IORING_SETUP_SQPOLL", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:72:48: [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).
strncat(flagstr, "IORING_SETUP_SQPOLL", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:76:4: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is low because the source is a
constant character.
strncat(flagstr, "|", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:76:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
strncat(flagstr, "|", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:77:3: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is low because the source is a
constant string.
strncat(flagstr, "IORING_SETUP_SQ_AFF", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:77:48: [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).
strncat(flagstr, "IORING_SETUP_SQ_AFF", 64 - strlen(flagstr));
data/liburing-0.7/test/io_uring_setup.c:178:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(fd, buf, 4096);
data/liburing-0.7/test/poll-cancel-ton.c:124:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(1000);
data/liburing-0.7/test/poll-many.c:60:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(p[off].fd[0], &c, 1);
data/liburing-0.7/test/poll-v-poll.c:109:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(100000);
data/liburing-0.7/test/poll-v-poll.c:148:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(100000);
data/liburing-0.7/test/poll-v-poll.c:278:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(100000);
data/liburing-0.7/test/send_recv.c:98:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (cqe->res -1 != strlen(str)) {
data/liburing-0.7/test/send_recv.c:100: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).
(int) strlen(str) + 1);
data/liburing-0.7/test/send_recvmsg.c:119:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (cqe->res -1 != strlen(str)) {
data/liburing-0.7/test/send_recvmsg.c:121: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).
(int) strlen(str) + 1);
data/liburing-0.7/test/splice.c:39:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(fd, buf, len);
data/liburing-0.7/test/stdout.c:27:32: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
memcpy(vecs[0].iov_base, str, strlen(str));
data/liburing-0.7/test/stdout.c:28:20: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
vecs[0].iov_len = strlen(str);
data/liburing-0.7/test/stdout.c:81:19: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (cqe->res != strlen(str)) {
data/liburing-0.7/test/stdout.c:83:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
cqe->res, (int)strlen(str),
data/liburing-0.7/test/stdout.c:87:50: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (cqe->user_data == 2 && memcmp(str, buffer, strlen(str))) {
data/liburing-0.7/test/stdout.c:111:29: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
memcpy(vecs.iov_base, str, strlen(str));
data/liburing-0.7/test/stdout.c:112:17: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
vecs.iov_len = strlen(str);
data/liburing-0.7/test/stdout.c:164:17: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
vecs.iov_len = strlen(vecs.iov_base);
data/liburing-0.7/test/submit-reuse.c:163:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(10000);
ANALYSIS SUMMARY:
Hits = 210
Lines analyzed = 19594 in approximately 0.48 seconds (41066 lines/second)
Physical Source Lines of Code (SLOC) = 15709
Hits@level = [0] 1124 [1] 61 [2] 141 [3] 2 [4] 6 [5] 0
Hits@level+ = [0+] 1334 [1+] 210 [2+] 149 [3+] 8 [4+] 6 [5+] 0
Hits/KSLOC@level+ = [0+] 84.9195 [1+] 13.3681 [2+] 9.48501 [3+] 0.509262 [4+] 0.381947 [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.