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/diod-1.0.24/diod/diod.c
Examining data/diod-1.0.24/diod/exp.c
Examining data/diod-1.0.24/diod/exp.h
Examining data/diod-1.0.24/diod/fid.c
Examining data/diod-1.0.24/diod/fid.h
Examining data/diod-1.0.24/diod/ioctx.c
Examining data/diod-1.0.24/diod/ioctx.h
Examining data/diod-1.0.24/diod/ops.h
Examining data/diod-1.0.24/diod/xattr.h
Examining data/diod-1.0.24/diod/ops.c
Examining data/diod-1.0.24/diod/xattr.c
Examining data/diod-1.0.24/libdiod/diod_auth.c
Examining data/diod-1.0.24/libdiod/diod_auth.h
Examining data/diod-1.0.24/libdiod/diod_conf.c
Examining data/diod-1.0.24/libdiod/diod_conf.h
Examining data/diod-1.0.24/libdiod/diod_log.c
Examining data/diod-1.0.24/libdiod/diod_log.h
Examining data/diod-1.0.24/libdiod/diod_rdma.c
Examining data/diod-1.0.24/libdiod/diod_rdma.h
Examining data/diod-1.0.24/libdiod/diod_sock.c
Examining data/diod-1.0.24/libdiod/diod_sock.h
Examining data/diod-1.0.24/liblsd/error.c
Examining data/diod-1.0.24/liblsd/hash.c
Examining data/diod-1.0.24/liblsd/hash.h
Examining data/diod-1.0.24/liblsd/hostlist.c
Examining data/diod-1.0.24/liblsd/hostlist.h
Examining data/diod-1.0.24/liblsd/list.c
Examining data/diod-1.0.24/liblsd/list.h
Examining data/diod-1.0.24/liblsd/thread.c
Examining data/diod-1.0.24/liblsd/thread.h
Examining data/diod-1.0.24/libnpclient/chmod.c
Examining data/diod-1.0.24/libnpclient/fid.c
Examining data/diod-1.0.24/libnpclient/fsys.c
Examining data/diod-1.0.24/libnpclient/mkdir.c
Examining data/diod-1.0.24/libnpclient/mount.c
Examining data/diod-1.0.24/libnpclient/mtfsys.c
Examining data/diod-1.0.24/libnpclient/npcimpl.h
Examining data/diod-1.0.24/libnpclient/npclient.h
Examining data/diod-1.0.24/libnpclient/open.c
Examining data/diod-1.0.24/libnpclient/pool.c
Examining data/diod-1.0.24/libnpclient/read.c
Examining data/diod-1.0.24/libnpclient/readdir.c
Examining data/diod-1.0.24/libnpclient/remove.c
Examining data/diod-1.0.24/libnpclient/stat.c
Examining data/diod-1.0.24/libnpclient/walk.c
Examining data/diod-1.0.24/libnpclient/write.c
Examining data/diod-1.0.24/libnpclient/xattr.c
Examining data/diod-1.0.24/libnpfs/9p.h
Examining data/diod-1.0.24/libnpfs/conn.c
Examining data/diod-1.0.24/libnpfs/ctl.c
Examining data/diod-1.0.24/libnpfs/error.c
Examining data/diod-1.0.24/libnpfs/fcall.c
Examining data/diod-1.0.24/libnpfs/fdtrans.c
Examining data/diod-1.0.24/libnpfs/fidpool.c
Examining data/diod-1.0.24/libnpfs/fmt.c
Examining data/diod-1.0.24/libnpfs/np.c
Examining data/diod-1.0.24/libnpfs/npfs.h
Examining data/diod-1.0.24/libnpfs/npfsimpl.h
Examining data/diod-1.0.24/libnpfs/npstring.c
Examining data/diod-1.0.24/libnpfs/rdmatrans.c
Examining data/diod-1.0.24/libnpfs/srv.c
Examining data/diod-1.0.24/libnpfs/trans.c
Examining data/diod-1.0.24/libnpfs/user.c
Examining data/diod-1.0.24/libnpfs/xpthread.h
Examining data/diod-1.0.24/tests/kern/dbench/child.c
Examining data/diod-1.0.24/tests/kern/dbench/dbench.c
Examining data/diod-1.0.24/tests/kern/dbench/dbench.h
Examining data/diod-1.0.24/tests/kern/dbench/fileio.c
Examining data/diod-1.0.24/tests/kern/dbench/io.c
Examining data/diod-1.0.24/tests/kern/dbench/snprintf.c
Examining data/diod-1.0.24/tests/kern/dbench/sockio.c
Examining data/diod-1.0.24/tests/kern/dbench/socklib.c
Examining data/diod-1.0.24/tests/kern/dbench/system.c
Examining data/diod-1.0.24/tests/kern/dbench/tbench_srv.c
Examining data/diod-1.0.24/tests/kern/dbench/util.c
Examining data/diod-1.0.24/tests/kern/fsstress/fsstress.c
Examining data/diod-1.0.24/tests/kern/fsstress/global.h
Examining data/diod-1.0.24/tests/kern/fsstress/xfscompat.h
Examining data/diod-1.0.24/tests/kern/fstest/fstest.c
Examining data/diod-1.0.24/tests/kern/fsx/fsx.c
Examining data/diod-1.0.24/tests/kern/kconjoin.c
Examining data/diod-1.0.24/tests/kern/pathwalk.c
Examining data/diod-1.0.24/tests/kern/postmark/postmark.c
Examining data/diod-1.0.24/tests/kern/tatomic.c
Examining data/diod-1.0.24/tests/kern/tcreate.c
Examining data/diod-1.0.24/tests/kern/test.h
Examining data/diod-1.0.24/tests/kern/tfcntl2.c
Examining data/diod-1.0.24/tests/kern/tfcntl3.c
Examining data/diod-1.0.24/tests/kern/tflock.c
Examining data/diod-1.0.24/tests/kern/tflock2.c
Examining data/diod-1.0.24/tests/kern/tfsgid.c
Examining data/diod-1.0.24/tests/kern/trename.c
Examining data/diod-1.0.24/tests/kern/tstat.c
Examining data/diod-1.0.24/tests/kern/tstatfs.c
Examining data/diod-1.0.24/tests/kern/tsuppgrp.c
Examining data/diod-1.0.24/tests/misc/tcap.c
Examining data/diod-1.0.24/tests/misc/tconf.c
Examining data/diod-1.0.24/tests/misc/test.h
Examining data/diod-1.0.24/tests/misc/tfcntl.c
Examining data/diod-1.0.24/tests/misc/tfidpool.c
Examining data/diod-1.0.24/tests/misc/tlist.c
Examining data/diod-1.0.24/tests/misc/tlua.c
Examining data/diod-1.0.24/tests/misc/tnpsrv.c
Examining data/diod-1.0.24/tests/misc/tnpsrv2.c
Examining data/diod-1.0.24/tests/misc/tnpsrv3.c
Examining data/diod-1.0.24/tests/misc/topt.c
Examining data/diod-1.0.24/tests/misc/tserialize.c
Examining data/diod-1.0.24/tests/misc/tsetfsuid.c
Examining data/diod-1.0.24/tests/misc/tsetfsuidsupp.c
Examining data/diod-1.0.24/tests/misc/tsetuid.c
Examining data/diod-1.0.24/tests/misc/tsuppgrp.c
Examining data/diod-1.0.24/tests/user/conjoin.c
Examining data/diod-1.0.24/tests/user/tattach.c
Examining data/diod-1.0.24/tests/user/tattachmt.c
Examining data/diod-1.0.24/tests/user/tflush.c
Examining data/diod-1.0.24/tests/user/tgetxattr.c
Examining data/diod-1.0.24/tests/user/tmkdir.c
Examining data/diod-1.0.24/tests/user/tread.c
Examining data/diod-1.0.24/tests/user/tremovexattr.c
Examining data/diod-1.0.24/tests/user/tstat.c
Examining data/diod-1.0.24/tests/user/twrite.c
Examining data/diod-1.0.24/tests/user/tsetxattr.c
Examining data/diod-1.0.24/tests/user/txattr.c
Examining data/diod-1.0.24/utils/diodcat.c
Examining data/diod-1.0.24/utils/dioddate.c
Examining data/diod-1.0.24/utils/diodload.c
Examining data/diod-1.0.24/utils/diodls.c
Examining data/diod-1.0.24/utils/diodmount.c
Examining data/diod-1.0.24/utils/diodshowmount.c
Examining data/diod-1.0.24/utils/dtop.c
Examining data/diod-1.0.24/utils/opt.c
Examining data/diod-1.0.24/utils/opt.h
Examining data/diod-1.0.24/utils/sample.c
Examining data/diod-1.0.24/utils/sample.h
FINAL RESULTS:
data/diod-1.0.24/diod/ops.c:880:14: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
if ((n = readlink (path_s (f->path), target, sizeof(target) - 1)) < 0) {
data/diod-1.0.24/diod/ops.c:955:13: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
if (chmod (path_s (f->path), mode) < 0) {
data/diod-1.0.24/libnpfs/fcall.c:824:24: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
if (!req->conn->srv->readlink) {
data/diod-1.0.24/libnpfs/fcall.c:828:26: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
rc = (*req->conn->srv->readlink)(fid);
data/diod-1.0.24/libnpfs/npfs.h:318:13: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
Npfcall* (*readlink)(Npfid *);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1122:9: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
rval = readlink(name->path, lbuf, lbufsiz);
data/diod-1.0.24/tests/kern/fstest/fstest.c:450:10: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
rval = chmod(STR(0), NUM(1));
data/diod-1.0.24/tests/kern/fstest/fstest.c:458:10: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
rval = chown(STR(0), NUM(1), NUM(2));
data/diod-1.0.24/utils/dtop.c:326:15: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
rename, readlink, getattr, setattr, link);
data/diod-1.0.24/libdiod/diod_conf.c:628: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.
if (config.configpath && access (config.configpath, R_OK) == 0)
data/diod-1.0.24/libdiod/diod_conf.c:718: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.
if (config.configpath && access (config.configpath, R_OK) == 0)
data/diod-1.0.24/libdiod/diod_log.c:214:5: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf (buf, sizeof (buf), fmt, ap); /* ignore overflow */
data/diod-1.0.24/libdiod/diod_log.c:231:5: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf (buf, sizeof (buf), fmt, ap); /* ignore overflow */
data/diod-1.0.24/libdiod/diod_log.h:8:33: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 1, 2), noreturn));
data/diod-1.0.24/libdiod/diod_log.h:10:33: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 1, 2)));
data/diod-1.0.24/libdiod/diod_log.h:12:33: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 2, 3), noreturn));
data/diod-1.0.24/libdiod/diod_log.h:14:33: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 2, 3)));
data/diod-1.0.24/libdiod/diod_log.h:16:33: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 1, 2), noreturn));
data/diod-1.0.24/libdiod/diod_log.h:18:33: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 1, 2)));
data/diod-1.0.24/liblsd/hostlist.c:343:11: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
len = vsnprintf(buf, 1024, msg, ap);
data/diod-1.0.24/liblsd/hostlist.c:2344:5: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat (buf, i->hr->prefix);
data/diod-1.0.24/liblsd/hostlist.c:2345:5: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat (buf, suffix);
data/diod-1.0.24/libnpfs/npfs.h:365:26: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 2, 3)));
data/diod-1.0.24/libnpfs/npfs.h:367:26: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 2, 3)));
data/diod-1.0.24/libnpfs/npfs.h:409:26: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 3,4)));
data/diod-1.0.24/libnpfs/npfs.h:411:26: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 3,4)));
data/diod-1.0.24/libnpfs/npstring.c:110:7: [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.
n = vsnprintf(s + slen, len - slen, fmt, vacpy);
data/diod-1.0.24/libnpfs/npstring.c:149:9: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf (s, len, fmt, ap); /* ignore overflow */
data/diod-1.0.24/libnpfs/npstring.c:162:6: [4] (buffer) sscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function. If the scanf format is influenceable by an
attacker, it's exploitable.
n = sscanf (s, "%as %d %d " \
data/diod-1.0.24/libnpfs/srv.c:881: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), fmt, ap);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:779: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.
int vsnprintf (char *str, size_t count, const char *fmt, va_list args)
data/diod-1.0.24/tests/kern/dbench/snprintf.c:794:6: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int snprintf(char *str,size_t count,const char *fmt,...)
data/diod-1.0.24/tests/kern/dbench/snprintf.c:800:8: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
ret = vsnprintf(str, count, fmt, ap);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:816:8: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
ret = vsnprintf(NULL, 0, format, ap2);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:824:8: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
ret = vsnprintf(*ptr, ret+1, format, ap2);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:848:6: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
int sprintf(char *str,const char *fmt,...);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:910:13: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int l1 = snprintf(NULL, 0, fp_fmt[x], fp_nums[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:911:13: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int l2 = snprintf(buf1, sizeof(buf1), fp_fmt[x], fp_nums[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:912:4: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf (buf2, fp_fmt[x], fp_nums[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:928:13: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int l1 = snprintf(NULL, 0, int_fmt[x], int_nums[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:929:13: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int l2 = snprintf(buf1, sizeof(buf1), int_fmt[x], int_nums[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:930:4: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf (buf2, int_fmt[x], int_nums[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:946:13: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int l1 = snprintf(NULL, 0, str_fmt[x], str_vals[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:947:13: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int l2 = snprintf(buf1, sizeof(buf1), str_fmt[x], str_vals[y]);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:948:4: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf (buf2, str_fmt[x], str_vals[y]);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:492:4: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(cmd,"rm -rf %s/*",dirname);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:493:4: [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.
system(cmd);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:537:2: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(&name->path[name->len], str);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1220:2: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(buf, name->path);
data/diod-1.0.24/tests/kern/fsx/fsx.c:184:2: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vfprintf(stderr, fmt, ap);
data/diod-1.0.24/tests/kern/fsx/fsx.c:207: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(buffer, BUF_SIZE, fmt, args);
data/diod-1.0.24/tests/kern/kconjoin.c:131:23: [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 ((cs = system (mntcmd)) == -1)
data/diod-1.0.24/tests/kern/kconjoin.c:137:23: [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 ((cs = system (tstcmd)) == -1)
data/diod-1.0.24/tests/kern/kconjoin.c:147:23: [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 ((cs = system (srvcmd)) == -1) {
data/diod-1.0.24/tests/kern/postmark/postmark.c:167:15: [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.
file_entry system;
data/diod-1.0.24/tests/kern/postmark/postmark.c:307:7: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(new_file_system->system.name,params);
data/diod-1.0.24/tests/kern/postmark/postmark.c:307:31: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
strcpy(new_file_system->system.name,params);
data/diod-1.0.24/tests/kern/postmark/postmark.c:308:24: [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.
new_file_system->system.size=weight;
data/diod-1.0.24/tests/kern/postmark/postmark.c:333:29: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
if (!strcmp(traverse->system.name,loc_name))
data/diod-1.0.24/tests/kern/postmark/postmark.c:335:40: [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.
file_system_weight-=traverse->system.size;
data/diod-1.0.24/tests/kern/postmark/postmark.c:676:7: [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(dest,
data/diod-1.0.24/tests/kern/postmark/postmark.c:678:7: [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(dest,SEPARATOR);
data/diod-1.0.24/tests/kern/postmark/postmark.c:683:7: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(conversion,"s%lu%s",RND(subdirectories),SEPARATOR);
data/diod-1.0.24/tests/kern/postmark/postmark.c:684:7: [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(dest,conversion);
data/diod-1.0.24/tests/kern/postmark/postmark.c:688:4: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(dest,conversion);
data/diod-1.0.24/tests/kern/postmark/postmark.c:910:36: [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.
for (count=0; count<list->system.size; count++)
data/diod-1.0.24/tests/kern/postmark/postmark.c:911:30: [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.
index[i++]=list->system.name;
data/diod-1.0.24/tests/kern/postmark/postmark.c:928:47: [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.
create_subdirectories(NULL,dir_list->system.name,subdirs);
data/diod-1.0.24/tests/kern/postmark/postmark.c:933:10: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(save_dir,"%s%s",base_dir,SEPARATOR);
data/diod-1.0.24/tests/kern/postmark/postmark.c:939:10: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(dir_name,"%ss%d",save_dir,i);
data/diod-1.0.24/tests/kern/postmark/postmark.c:957:47: [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.
delete_subdirectories(NULL,dir_list->system.name,subdirs);
data/diod-1.0.24/tests/kern/postmark/postmark.c:962:10: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(save_dir,"%s%s",base_dir,SEPARATOR);
data/diod-1.0.24/tests/kern/postmark/postmark.c:968:10: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(dir_name,"%ss%d",save_dir,i);
data/diod-1.0.24/tests/kern/postmark/postmark.c:1109:45: [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.
printf("\t%s (weight=%d)\n",traverse->system.name,traverse->system.size);
data/diod-1.0.24/tests/kern/postmark/postmark.c:1109:67: [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.
printf("\t%s (weight=%d)\n",traverse->system.name,traverse->system.size);
data/diod-1.0.24/tests/kern/postmark/postmark.c:1190:7: [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.
system((strlen(buffer)>1)?buffer+1:getenv("SHELL"));
data/diod-1.0.24/tests/kern/tfsgid.c:34: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.
if (access (argv[2], F_OK) == 0)
data/diod-1.0.24/tests/user/conjoin.c:105:23: [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 ((cs = system (cmd2)) == -1)
data/diod-1.0.24/tests/user/conjoin.c:117:23: [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 ((cs = system (cmd1)) == -1)
data/diod-1.0.24/utils/diodmount.c:380: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.
if (access && opt_scanf (o, "access=%d", &access_uid)) {
data/diod-1.0.24/utils/diodmount.c:387: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.
if (!uname && !access) {
data/diod-1.0.24/utils/diodmount.c:391:26: [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.
} else if (uname && !access) {
data/diod-1.0.24/utils/diodmount.c:397:26: [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.
} else if (!uname && access) {
data/diod-1.0.24/utils/diodmount.c:398:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (strcmp (access, "user") == 0)
data/diod-1.0.24/utils/diodmount.c:403:50: [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.
msg_exit ("unsupported -oaccess=%s", access);
data/diod-1.0.24/utils/diodmount.c:405:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (strcmp (access, "user") == 0) {
data/diod-1.0.24/utils/diodmount.c:412:50: [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.
msg_exit ("unsupported -oaccess=%s", access);
data/diod-1.0.24/utils/diodmount.c:698:13: [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.
system ("/sbin/modprobe 9nbd");
data/diod-1.0.24/utils/dtop.c:67:29: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 4, 5)));
data/diod-1.0.24/utils/dtop.c:702:5: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (tp->key.host, key->host);
data/diod-1.0.24/utils/dtop.c:703:5: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (tp->key.aname, key->aname);
data/diod-1.0.24/utils/opt.c:199:15: [4] (buffer) vsscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function. If the scanf format is influenceable by an
attacker, it's exploitable.
ret = vsscanf (item, fmt, vacpy);
data/diod-1.0.24/utils/opt.h:10:51: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute__ ((format (printf, 2, 3)));
data/diod-1.0.24/utils/opt.h:17:51: [4] (buffer) scanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function.
__attribute__ ((format (scanf, 2, 3)));
data/diod-1.0.24/diod/diod.c:81:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/diod/diod.c:104:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/tests/kern/dbench/fileio.c:120:7: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
if (random() % 10 < 2) {
data/diod-1.0.24/tests/kern/dbench/tbench_srv.c:96:14: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((c = getopt(argc, argv, "t:")) != -1) {
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:307:14: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((c = getopt(argc, argv, "cd:e:f:i:l:n:p:rs:vwzHSX")) != -1) {
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:432:6: [3] (random) srandom:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srandom(seed);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:433:10: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
j = random() % 100;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:436:14: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
(void) random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:438:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
errtag = (random() % (XFS_ERRTAG_MAX-1)) + 1;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:441:5: [3] (random) srandom:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srandom(seed);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:442:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
j = random() % 100;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:445:13: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
(void) random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:447:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
errtag += (random() % (XFS_ERRTAG_MAX - errtag));
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:728:2: [3] (random) srandom:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srandom(seed);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:730:14: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
namerand = random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:732:23: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
p = &ops[freq_table[random() % freq_table_size]];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:735:17: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
p->func(opno, random());
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1430:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1430:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1480:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
which = (int)(random() % total);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1531:13: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
li = (int)(random() % (sizeof(lengths) / sizeof(lengths[0])));
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1532:14: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
len = (int)(random() % lengths[li]);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1591:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
good = random() & 1;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1646:13: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
u = (uid_t)random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1647:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
nbits = (int)(random() % 32);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1677:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
type = rtpct ? ((random() % 100) > rtpct ? FT_REG : FT_RTF) : FT_REG;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1679:14: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
extsize = (random() % 10) + 1;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1821:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1821:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1825:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
len = (random() % (getpagesize() * 32)) + 1;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1906:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1906:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1910:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
len = (random() % (getpagesize() * 32)) + 1;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2000:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2000:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2095:26: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
if (!get_fname(FT_DIRm, random(), NULL, NULL, &fep, &v))
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2242:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2242:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2245:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
len = (random() % (getpagesize() * 32)) + 1;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2300:26: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
if (!get_fname(FT_DIRm, random(), NULL, NULL, &dfep, &v))
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2373:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2373:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2378:23: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
fl.l_len = (off64_t)(random() % (1024 * 1024));
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2464:14: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
len = (int)(random() % PATH_MAX);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2516:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2516:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2590:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2590:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2595:23: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
fl.l_len = (off64_t)(random() % (1 << 20));
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2643:19: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2643:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
lr = ((__int64_t)random() << 32) + random();
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2647:9: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
len = (random() % (getpagesize() * 32)) + 1;
data/diod-1.0.24/tests/kern/fstest/fstest.c:555:15: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((ch = getopt(argc, argv, "g:u:U:")) != -1) {
data/diod-1.0.24/tests/kern/fsx/fsx.c:903:14: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
keep_size = random() % 2;
data/diod-1.0.24/tests/kern/fsx/fsx.c:1008:21: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
unsigned long rv = random();
data/diod-1.0.24/tests/kern/fsx/fsx.c:1025:11: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
offset = random();
data/diod-1.0.24/tests/kern/fsx/fsx.c:1027:10: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
size = random() % (maxoplen + 1);
data/diod-1.0.24/tests/kern/fsx/fsx.c:1081:11: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
size = random() % maxfilelen;
data/diod-1.0.24/tests/kern/fsx/fsx.c:1354:15: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((ch = getopt(argc, argv, "b:c:dfl:m:no:p:qr:s:t:w:xyAD:FHLN:OP:RS:WZ"))
data/diod-1.0.24/tests/kern/fsx/fsx.c:1513:2: [3] (random) setstate:
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.
setstate(state);
data/diod-1.0.24/tests/kern/fsx/fsx.c:1574:21: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
original_buf[i] = random() % 256;
data/diod-1.0.24/tests/kern/pathwalk.c:54:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/tests/kern/pathwalk.c:67:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/tests/kern/postmark/postmark.c:68:14: [3] (buffer) getwd:
This does not protect against buffer overflows by itself, so use with
caution (CWE-120, CWE-20). Use getcwd instead.
extern char *getwd();
data/diod-1.0.24/tests/kern/postmark/postmark.c:1190:42: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
system((strlen(buffer)>1)?buffer+1:getenv("SHELL"));
data/diod-1.0.24/tests/misc/tconf.c:24:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/tests/misc/tconf.c:32:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/diodcat.c:58:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/diodcat.c:69:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/dioddate.c:60:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/dioddate.c:70:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/diodload.c:61:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/diodload.c:71:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/diodls.c:62:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/diodls.c:73:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/diodmount.c:76:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/diodmount.c:87:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/diodshowmount.c:59:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/diodshowmount.c:69:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/utils/dtop.c:71:32: [3] (buffer) getopt_long:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt_long (ac,av,opt,lopt,NULL)
data/diod-1.0.24/utils/dtop.c:79:32: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
#define GETOPT(ac,av,opt,lopt) getopt (ac,av,opt)
data/diod-1.0.24/diod/diod.c:346:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char rdir[PATH_MAX];
data/diod-1.0.24/diod/ioctx.c:190:17: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
ioctx->fd = open (path->s, flags, mode);
data/diod-1.0.24/diod/ioctx.c:468:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (s, opath->s, opath->len);
data/diod-1.0.24/diod/ioctx.c:470:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (s + opath->len + 1, ns->str, ns->len);
data/diod-1.0.24/diod/ops.c:877:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char target[PATH_MAX + 1];
data/diod-1.0.24/diod/ops.c:1075:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char path[PATH_MAX + 1];
data/diod-1.0.24/diod/xattr.c:136:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (x->buf + offset, buf, len);
data/diod-1.0.24/diod/xattr.c:153:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (buf, x->buf + offset, len);
data/diod-1.0.24/libdiod/diod_auth.c:179:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char a[128];
data/diod-1.0.24/libdiod/diod_auth.c:256:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (da->datastr + offset, data, count);
data/diod-1.0.24/libdiod/diod_conf.c:422:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char *p, *path, buf[1024];
data/diod-1.0.24/libdiod/diod_conf.c:428:15: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if (!(f = fopen (_PATH_PROC_MOUNTS, "r")))
data/diod-1.0.24/libdiod/diod_log.c:172:23: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
else if ((f = fopen (s, "a"))) {
data/diod-1.0.24/libdiod/diod_log.c:210:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[128];
data/diod-1.0.24/libdiod/diod_log.c:211:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char errbuf[64];
data/diod-1.0.24/libdiod/diod_log.c:229:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024]; /* make it large enough for protocol debug output */
data/diod-1.0.24/libdiod/diod_sock.c:331:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char host[NI_MAXHOST], ip[NI_MAXHOST], svc[NI_MAXSERV];
data/diod-1.0.24/liblsd/hostlist.c:339:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/diod-1.0.24/liblsd/hostlist.c:517:9: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(hn->prefix, hostname, idx + 1);
data/diod-1.0.24/liblsd/hostlist.c:1267:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char prefix[256] = "";
data/diod-1.0.24/liblsd/hostlist.c:1312:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(prefix, tok, (size_t) pos * sizeof(char));
data/diod-1.0.24/liblsd/hostlist.c:1491:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char host[4096];
data/diod-1.0.24/liblsd/hostlist.c:1516:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char cur_tok[1024];
data/diod-1.0.24/liblsd/hostlist.c:1743:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[MAXHOSTRANGELEN + 1];
data/diod-1.0.24/liblsd/hostlist.c:1776:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/diod-1.0.24/liblsd/hostlist.c:1847:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[MAXHOSTNAMELEN + 16];
data/diod-1.0.24/liblsd/hostlist.c:2322:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char suffix[16];
data/diod-1.0.24/liblsd/hostlist.c:2353:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[MAXHOSTRANGELEN + 1];
data/diod-1.0.24/liblsd/hostlist.c:2624:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/diod-1.0.24/liblsd/hostlist.c:2665:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024000];
data/diod-1.0.24/libnpclient/read.c:159: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 (fid->buf + fid->buf_size, buf, len);
data/diod-1.0.24/libnpclient/read.c:164: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 (fid->buf, buf, len);
data/diod-1.0.24/libnpclient/read.c:180: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, fid->buf, ret);
data/diod-1.0.24/libnpclient/readdir.c:63: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 (data, rc->u.rreaddir.data, rc->u.rreaddir.count);
data/diod-1.0.24/libnpclient/walk.c:77: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 *wnames[P9_MAXWELEM];
data/diod-1.0.24/libnpfs/conn.c:139: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 s[512];
data/diod-1.0.24/libnpfs/ctl.c:153: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 path[PATH_MAX + 1];
data/diod-1.0.24/libnpfs/ctl.c:163: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).
if ((fd = open (path, O_RDONLY)) < 0) {
data/diod-1.0.24/libnpfs/fcall.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 a[128];
data/diod-1.0.24/libnpfs/fcall.c:144: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 a[128];
data/diod-1.0.24/libnpfs/fdtrans.c:155:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (fdt->fc->pkt, fc->pkt + size, fdt->fc_len);
data/diod-1.0.24/libnpfs/fmt.c:46:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[10];
data/diod-1.0.24/libnpfs/npfs.h:172: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 client_id[128];
data/diod-1.0.24/libnpfs/rdmatrans.c:81:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char buf[0];
data/diod-1.0.24/libnpfs/srv.c:769: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[STATIC_RLERROR_SIZE];
data/diod-1.0.24/libnpfs/srv.c:779: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[STATIC_RFLUSH_SIZE];
data/diod-1.0.24/libnpfs/srv.c:876: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[128];
data/diod-1.0.24/libnpfs/srv.c:877: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 ebuf[64];
data/diod-1.0.24/libnpfs/user.c:299: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 ustr[32] = "root";
data/diod-1.0.24/tests/kern/dbench/child.c:166:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char line[1024], fname[1024], fname2[1024];
data/diod-1.0.24/tests/kern/dbench/child.c:185:6: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
f = fopen(loadfile, "r");
data/diod-1.0.24/tests/kern/dbench/dbench.c:55:11: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((f = fopen(options.loadfile, "rt")) != NULL)
data/diod-1.0.24/tests/kern/dbench/dbench.c:455:19: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
options.nprocs = atoi(extra_argv[0]);
data/diod-1.0.24/tests/kern/dbench/fileio.c:62: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).
dir_fd = open(copy_name, O_RDONLY);
data/diod-1.0.24/tests/kern/dbench/fileio.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[44];
data/diod-1.0.24/tests/kern/dbench/fileio.c:102: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[44];
data/diod-1.0.24/tests/kern/dbench/fileio.c:116: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[44];
data/diod-1.0.24/tests/kern/dbench/fileio.c:122: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(buf, &t, sizeof(t));
data/diod-1.0.24/tests/kern/dbench/fileio.c:125: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(buf, &tv, sizeof(tv));
data/diod-1.0.24/tests/kern/dbench/fileio.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(fname, flags, 0600);
data/diod-1.0.24/tests/kern/dbench/fileio.c:288: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(fname, flags, 0600);
data/diod-1.0.24/tests/kern/dbench/fileio.c:346:24: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
if (c == ((unsigned char *)buf)[0]) {
data/diod-1.0.24/tests/kern/dbench/fileio.c:351:25: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
} else if (((unsigned char *)buf)[0] == 0) {
data/diod-1.0.24/tests/kern/dbench/io.c:27: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 buf[70000];
data/diod-1.0.24/tests/kern/dbench/io.c:66: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, flags, 0600);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:469: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 convert[20];
data/diod-1.0.24/tests/kern/dbench/snprintf.c:622: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 iconvert[311];
data/diod-1.0.24/tests/kern/dbench/snprintf.c:623: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 fconvert[311];
data/diod-1.0.24/tests/kern/dbench/snprintf.c:852: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 buf1[1024];
data/diod-1.0.24/tests/kern/dbench/snprintf.c:853: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 buf2[1024];
data/diod-1.0.24/tests/kern/dbench/snprintf.c:971: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(buf2, "%1.1f", r);
data/diod-1.0.24/tests/kern/dbench/sockio.c:24: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[70000];
data/diod-1.0.24/tests/kern/dbench/socklib.c:72: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(&sock_out.sin_addr, hp->h_addr, hp->h_length);
data/diod-1.0.24/tests/kern/dbench/socklib.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 tok[200];
data/diod-1.0.24/tests/kern/dbench/socklib.c:151:12: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
value = atoi(p+1);
data/diod-1.0.24/tests/kern/dbench/tbench_srv.c:27: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[70000];
data/diod-1.0.24/tests/kern/dbench/util.c:89: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(p, insert, li);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:279:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[10];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:287: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 cmd[256];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:338:12: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
loops = atoi(optarg);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:341:17: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
operations = atoi(optarg);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:344:12: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
nproc = atoi(optarg);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:407: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, "fss%x", getpid());
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:546: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:566: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:586: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:622: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:714:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[10];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:719: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, "p%x", procid);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:754: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:765:6: [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.
i = sprintf(buf, "%c%x", flp->tag, fep->id);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:799: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:806:8: [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.
len = sprintf(buf, "%c%x", flp->tag, id = nameseq++);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:888: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:907: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 buf1[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:908: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 buf2[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:962: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:998: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1017: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1058: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1062: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).
rval = open(name->path, oflag);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1077: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1107:14: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
p->freq = atoi(s);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1118: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1137: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 buf1[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1138: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 buf2[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1192: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1265: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1284: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1308: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1327: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[MAXNAMELEN];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1450: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/diod-1.0.24/tests/kern/fsstress/fsstress.c:1518: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 aname[10];
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1530: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(aname, "a%x", nameseq++);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1561: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(".", O_RDONLY);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1618: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(".", O_RDONLY);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2259: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[PATH_MAX];
data/diod-1.0.24/tests/kern/fstest/fstest.c:253:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char sflags[1024];
data/diod-1.0.24/tests/kern/fstest/fstest.c:414: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).
rval = open(STR(0), flags, (mode_t)NUM(2));
data/diod-1.0.24/tests/kern/fstest/fstest.c:420: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).
rval = open(STR(0), flags);
data/diod-1.0.24/tests/kern/fstest/fstest.c:424: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).
rval = open(STR(0), O_CREAT | O_EXCL, NUM(1));
data/diod-1.0.24/tests/kern/fstest/fstest.c:627: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 errnum[8];
data/diod-1.0.24/tests/kern/fsx/fsx.c:120:1: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char state[256];
data/diod-1.0.24/tests/kern/fsx/fsx.c:204: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[BUF_SIZE];
data/diod-1.0.24/tests/kern/fsx/fsx.c:245: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 *falloc_type[3] = {"PAST_EOF", "EXTENDING", "INTERIOR"};
data/diod-1.0.24/tests/kern/fsx/fsx.c:636: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(temp_buf, p + pg_offset, size);
data/diod-1.0.24/tests/kern/fsx/fsx.c:784: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(p + pg_offset, good_buf + offset, size);
data/diod-1.0.24/tests/kern/fsx/fsx.c:986: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_RDWR|o_direct, 0);
data/diod-1.0.24/tests/kern/fsx/fsx.c:1341: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 goodfile[1024];
data/diod-1.0.24/tests/kern/fsx/fsx.c:1342: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 logfile[1024];
data/diod-1.0.24/tests/kern/fsx/fsx.c:1514: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,
data/diod-1.0.24/tests/kern/fsx/fsx.c:1538:2: [2] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant string.
strcat (goodfile, ".fsxgood");
data/diod-1.0.24/tests/kern/fsx/fsx.c:1539: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).
fsxgoodfd = open(goodfile, O_RDWR|O_CREAT|O_TRUNC, 0666);
data/diod-1.0.24/tests/kern/fsx/fsx.c:1545:2: [2] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant string.
strcat (logfile, ".fsxlog");
data/diod-1.0.24/tests/kern/fsx/fsx.c:1546:12: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fsxlogf = fopen(logfile, "w");
data/diod-1.0.24/tests/kern/kconjoin.c:60:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char fqcmd[PATH_MAX];
data/diod-1.0.24/tests/kern/pathwalk.c:222:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char path[PATH_MAX + 1];
data/diod-1.0.24/tests/kern/pathwalk.c:239:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[PATH_MAX + 1];
data/diod-1.0.24/tests/kern/pathwalk.c:266:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char path[PATH_MAX + 1];
data/diod-1.0.24/tests/kern/pathwalk.c:283:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char path[PATH_MAX + 1];
data/diod-1.0.24/tests/kern/pathwalk.c:302:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char path[PATH_MAX + 1];
data/diod-1.0.24/tests/kern/postmark/postmark.c:159:4: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[MAX_FILENAME+1]; /* name of individual file */
data/diod-1.0.24/tests/kern/postmark/postmark.c:186: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.
static char buffer[MAX_LINE]; /* storage for current conversion */
data/diod-1.0.24/tests/kern/postmark/postmark.c:189:7: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buffer,"%.2f megabytes",(float)i/MEGABYTE);
data/diod-1.0.24/tests/kern/postmark/postmark.c:192:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buffer,"%.2f kilobytes",(float)i/KILOBYTE);
data/diod-1.0.24/tests/kern/postmark/postmark.c:194:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buffer,"%d bytes",i);
data/diod-1.0.24/tests/kern/postmark/postmark.c:203: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.
static char buffer[MAX_LINE]; /* storage for current conversion */
data/diod-1.0.24/tests/kern/postmark/postmark.c:206:7: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buffer,"%.2f megabytes",i/(float)MEGABYTE);
data/diod-1.0.24/tests/kern/postmark/postmark.c:209:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buffer,"%.2f kilobytes",i/(float)KILOBYTE);
data/diod-1.0.24/tests/kern/postmark/postmark.c:211:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(buffer,"%f bytes",i);
data/diod-1.0.24/tests/kern/postmark/postmark.c:223:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (size=atoi(param))>0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:226:46: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if ((token=strchr(param,' ')) && (size=atoi(token))>0 &&
data/diod-1.0.24/tests/kern/postmark/postmark.c:244:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (size=atoi(param))>0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:258:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (size=atoi(param))>0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:272:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (size=atoi(param))>0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:289:19: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if ((weight=atoi(split+1))<=0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:414:26: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (subdirs=atoi(param))>=0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:428:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (size=atoi(param))>0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:442:23: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (size=atoi(param))>0)
data/diod-1.0.24/tests/kern/postmark/postmark.c:469:24: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (value=atoi(param))>=-1 && value<=10)
data/diod-1.0.24/tests/kern/postmark/postmark.c:484:24: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
if (param && (value=atoi(param))>=-1 && value<=10)
data/diod-1.0.24/tests/kern/postmark/postmark.c:671: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 conversion[MAX_LINE+1];
data/diod-1.0.24/tests/kern/postmark/postmark.c:687: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(conversion,"%d",++files_created);
data/diod-1.0.24/tests/kern/postmark/postmark.c:707:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fp=fopen(file_table[free_file].name,"w");
data/diod-1.0.24/tests/kern/postmark/postmark.c:709: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).
fd=open(file_table[free_file].name,O_RDWR|O_CREAT,0644);
data/diod-1.0.24/tests/kern/postmark/postmark.c:756:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fp=fopen(file_table[number].name,"r");
data/diod-1.0.24/tests/kern/postmark/postmark.c:758: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).
fd=open(file_table[number].name,O_RDONLY,0644);
data/diod-1.0.24/tests/kern/postmark/postmark.c:802:13: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fp=fopen(file_table[number].name,"a");
data/diod-1.0.24/tests/kern/postmark/postmark.c:804: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).
fd=open(file_table[number].name,O_RDWR|O_APPEND,0644);
data/diod-1.0.24/tests/kern/postmark/postmark.c:921: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 dir_name[MAX_LINE+1]; /* buffer holding subdirectory names */
data/diod-1.0.24/tests/kern/postmark/postmark.c:922: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 save_dir[MAX_LINE+1];
data/diod-1.0.24/tests/kern/postmark/postmark.c:950: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 dir_name[MAX_LINE+1]; /* buffer holding subdirectory names */
data/diod-1.0.24/tests/kern/postmark/postmark.c:951: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 save_dir[MAX_LINE+1];
data/diod-1.0.24/tests/kern/postmark/postmark.c:1057:15: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fp=fopen(param,"a"))==NULL)
data/diod-1.0.24/tests/kern/postmark/postmark.c:1082: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 current_dir[MAX_LINE+1]; /* buffer containing working directory */
data/diod-1.0.24/tests/kern/postmark/postmark.c:1087:15: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fp=fopen(param,"a"))==NULL)
data/diod-1.0.24/tests/kern/postmark/postmark.c:1173:10: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer,"help");
data/diod-1.0.24/tests/kern/postmark/postmark.c:1175:10: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer,"quit");
data/diod-1.0.24/tests/kern/postmark/postmark.c:1218:12: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fp=fopen(filename,"r"))) /* open config file */
data/diod-1.0.24/tests/kern/postmark/postmark.c:1237: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 buffer[MAX_LINE+1]; /* storage for input command line */
data/diod-1.0.24/tests/kern/tatomic.c:15: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).
fd = open(argv[1], O_CREAT|O_WRONLY, 0644);
data/diod-1.0.24/tests/kern/tatomic.c:23: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).
fd = open(argv[1], O_CREAT|O_EXCL, 0644);
data/diod-1.0.24/tests/kern/test.h:46:14: [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).
int fd = mkstemp (p);
data/diod-1.0.24/tests/kern/tfcntl2.c:63:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:75:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:100:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:112:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:137:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:149:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:173:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:186:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:211:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl2.c:224:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:63:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:79:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:86: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).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:101:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:118:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:135:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:151:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDONLY)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:163:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_WRONLY)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:176:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDONLY)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:189:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_WRONLY)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:202:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:236:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:243: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).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tfcntl3.c:257:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock.c:44:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock.c:55:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock.c:79:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock.c:90:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock.c:114:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock.c:125:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd2 = open (argv[1], O_RDWR)) < 0)
data/diod-1.0.24/tests/kern/tflock2.c:22:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[1], O_RDWR)) < 0) {
data/diod-1.0.24/tests/kern/tflock2.c:32: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).
if ((fd2 = open (argv[1], O_RDWR)) < 0) {
data/diod-1.0.24/tests/kern/tfsgid.c:36:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (argv[2], O_CREAT, 0644)) < 0)
data/diod-1.0.24/tests/kern/tsuppgrp.c:36:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[256];
data/diod-1.0.24/tests/misc/test.h:46:14: [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).
int fd = mkstemp (p);
data/diod-1.0.24/tests/misc/tfcntl.c:60:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/diod-1.0.24/tests/misc/tfcntl.c:68:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (path, O_RDWR)) < 0)
data/diod-1.0.24/tests/misc/tfcntl.c:174:23: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (path, O_RDWR)) < 0)
data/diod-1.0.24/tests/misc/tnpsrv2.c:46:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tmpstr[PATH_MAX + 1];
data/diod-1.0.24/tests/misc/tnpsrv2.c:50:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char dbuf[TEST_MSIZE - P9_IOHDRSZ];
data/diod-1.0.24/tests/misc/tserialize.c:114:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char s[256];
data/diod-1.0.24/tests/misc/tserialize.c:125:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (fc2->pkt, fc->pkt, fc->size);
data/diod-1.0.24/tests/misc/tserialize.c:147:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[STATIC_RLERROR_SIZE];
data/diod-1.0.24/tests/misc/tserialize.c:588:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char *name[3] = { "abc", "def", "ghi" }, name2[3][128];
data/diod-1.0.24/tests/misc/tserialize.c:944:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[STATIC_RFLUSH_SIZE];
data/diod-1.0.24/tests/misc/tserialize.c:1001:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char *wnames[P9_MAXWELEM] = {
data/diod-1.0.24/tests/misc/tsetfsuidsupp.c:67:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (path, O_RDONLY)) < 0) {
data/diod-1.0.24/tests/misc/tsuppgrp.c:37:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[256];
data/diod-1.0.24/tests/user/conjoin.c:56:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char fqcmd[PATH_MAX];
data/diod-1.0.24/tests/user/tread.c:71:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (outfile, O_WRONLY | O_CREAT, 0644)) < 0)
data/diod-1.0.24/tests/user/twrite.c:69:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ((fd = open (infile, O_RDONLY)) < 0)
data/diod-1.0.24/utils/diodls.c:170:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char s[16];
data/diod-1.0.24/utils/diodls.c:200:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char uid[16], gid[16];
data/diod-1.0.24/utils/diodmount.c:600:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char s[64], *addr;
data/diod-1.0.24/utils/diodmount.c:681:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char uname[256];
data/diod-1.0.24/utils/diodmount.c:696: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).
fd = open (dev, O_RDWR);
data/diod-1.0.24/utils/diodmount.c:699:18: [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, O_RDWR);
data/diod-1.0.24/utils/diodmount.c:749: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).
fd = open (dev, O_RDWR);
data/diod-1.0.24/utils/diodshowmount.c:98:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[80], *host, *p;
data/diod-1.0.24/utils/diodshowmount.c:166:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char s[1024];
data/diod-1.0.24/utils/dtop.c:87:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char host[MAXHOSTNAMELEN];
data/diod-1.0.24/utils/dtop.c:88:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char aname[PATH_MAX];
data/diod-1.0.24/utils/sample.c:71:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (s, s1, sizeof (*s));
data/diod-1.0.24/diod/diod.c:604:5: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (0);
data/diod-1.0.24/diod/exp.c:109:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int xlen = strlen (x->path);
data/diod-1.0.24/diod/exp.c:110:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int plen = strlen (path);
data/diod-1.0.24/diod/ops.c:257: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).
if (!fid || !fid->aname || strlen (fid->aname) == 0)
data/diod-1.0.24/diod/ops.c:359:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int plen = strlen (path) + 4;
data/diod-1.0.24/libdiod/diod_auth.c:244: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).
} else if (da->datastr && offset == strlen (da->datastr)) {
data/diod-1.0.24/libdiod/diod_conf.c:431: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).
if (buf[strlen(buf) - 1] == '\n')
data/diod-1.0.24/libdiod/diod_conf.c:432: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).
buf[strlen(buf) - 1] = '\0';
data/diod-1.0.24/libdiod/diod_sock.c:227:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (addr.sun_path, path, sizeof (addr.sun_path) - 1);
data/diod-1.0.24/libdiod/diod_sock.c:229:16: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
oldumask = umask (0111);
data/diod-1.0.24/libdiod/diod_sock.c:231:5: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (oldumask);
data/diod-1.0.24/libdiod/diod_sock.c:370:37: [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).
diod_sock_startfd (srv, fd, fd, strlen(host) > 0 ? host : ip, flags);
data/diod-1.0.24/libdiod/diod_sock.c:473:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (addr.sun_path, path, sizeof (addr.sun_path) - 1);
data/diod-1.0.24/liblsd/hostlist.c:475: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).
int idx = strlen(hostname) - 1;
data/diod-1.0.24/liblsd/hostlist.c:501:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (idx == strlen(hostname) - 1) {
data/diod-1.0.24/liblsd/hostlist.c:567: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).
return (int) strlen(hn->suffix);
data/diod-1.0.24/liblsd/hostlist.c:803:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size = strlen(hr->prefix) + hr->width + 16;
data/diod-1.0.24/liblsd/hostlist.c:826:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size = strlen(hr->prefix) + hr->width + 16;
data/diod-1.0.24/liblsd/hostlist.c:942: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).
len_hn = strlen (hn->prefix);
data/diod-1.0.24/liblsd/hostlist.c:964: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).
len_hr = strlen (hr->prefix);
data/diod-1.0.24/liblsd/hostlist.c:1277: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).
if (str == NULL || strlen(str) == 0)
data/diod-1.0.24/liblsd/hostlist.c:1293: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).
pos = strlen(tok) - 1;
data/diod-1.0.24/liblsd/hostlist.c:1305: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).
pos = strlen(tok) - 1;
data/diod-1.0.24/liblsd/hostlist.c:1342:28: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (pos != strlen(prefix) ||
data/diod-1.0.24/liblsd/hostlist.c:1439: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).
range->width = strlen(str);
data/diod-1.0.24/liblsd/hostlist.c:1527:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(cur_tok, tok, 1024);
data/diod-1.0.24/liblsd/hostlist.c:2339:11: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen (i->hr->prefix) + strlen (suffix) + 1;
data/diod-1.0.24/liblsd/hostlist.c:2339:36: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen (i->hr->prefix) + strlen (suffix) + 1;
data/diod-1.0.24/libnpclient/write.c:105: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).
int n, count = strlen (buf), done = 0;
data/diod-1.0.24/libnpfs/ctl.c:159: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).
for (n = 0; n < strlen (path); n++) {
data/diod-1.0.24/libnpfs/ctl.c:180:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
n = read (fd, s + len, ssize - len - 1);
data/diod-1.0.24/libnpfs/ctl.c:445: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 (100*1000);
data/diod-1.0.24/libnpfs/ctl.c:458: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).
len = f->data ? strlen (f->data) : 0;
data/diod-1.0.24/libnpfs/ctl.c:544: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 (100*1000);
data/diod-1.0.24/libnpfs/fcall.c:443:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
n = conn->srv->auth->read(fid, tc->u.tread.offset, tc->u.tread.count, rc->u.rread.data);
data/diod-1.0.24/libnpfs/fcall.c:460:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!conn->srv->read) {
data/diod-1.0.24/libnpfs/fcall.c:464:21: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = (*conn->srv->read)(fid, tc->u.tread.offset,
data/diod-1.0.24/libnpfs/fdtrans.c:131:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
n = read(fdt->fdin, fc->pkt + len, msize - len);
data/diod-1.0.24/libnpfs/fmt.c:82: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(s);
data/diod-1.0.24/libnpfs/np.c:151:10: [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).
slen = strlen(s);
data/diod-1.0.24/libnpfs/np.c:303: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).
int size = sizeof(msize) + sizeof(u16) + strlen(version);
data/diod-1.0.24/libnpfs/np.c:320: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).
+ sizeof(u16) + (version ? strlen(version) : 0);
data/diod-1.0.24/libnpfs/np.c:337: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).
+ sizeof(u16) + (uname ? strlen (uname) : 0)
data/diod-1.0.24/libnpfs/np.c:338: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).
+ sizeof(u16) + (aname ? strlen (aname) : 0)
data/diod-1.0.24/libnpfs/np.c:415: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).
+ sizeof(u16) + (uname ? strlen(uname) : 0)
data/diod-1.0.24/libnpfs/np.c:416: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).
+ sizeof(u16) + (aname ? strlen(aname) : 0)
data/diod-1.0.24/libnpfs/np.c:458:39: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size += sizeof(u16) + strlen(wnames[i]);
data/diod-1.0.24/libnpfs/np.c:744: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).
int size = sizeof(u32) + sizeof(u16) + strlen(name)
data/diod-1.0.24/libnpfs/np.c:780: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).
int size = sizeof(u32) + sizeof(u16) + strlen(name)
data/diod-1.0.24/libnpfs/np.c:781: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).
+ sizeof(u16) + strlen(symtgt) + sizeof(u32);
data/diod-1.0.24/libnpfs/np.c:814: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).
int size = sizeof(u32) + sizeof(u16) + strlen(name)
data/diod-1.0.24/libnpfs/np.c:850:55: [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 size = sizeof(u32) + sizeof(u32) + sizeof(u16) + strlen(name);
data/diod-1.0.24/libnpfs/np.c:897: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).
int size = sizeof(u16) + strlen(target);
data/diod-1.0.24/libnpfs/np.c:1008:51: [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 size = 2*sizeof(u32) + sizeof(u16) + (name ? strlen (name) : 0);
data/diod-1.0.24/libnpfs/np.c:1041: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).
+ sizeof(u16) + (name ? strlen (name) : 0)
data/diod-1.0.24/libnpfs/np.c:1153:34: [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).
+ sizeof(u32) + sizeof(u16) + strlen(client_id);
data/diod-1.0.24/libnpfs/np.c:1191: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).
+ sizeof(u16) + strlen(client_id);
data/diod-1.0.24/libnpfs/np.c:1212: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).
+ sizeof(u16) + strlen(client_id);
data/diod-1.0.24/libnpfs/np.c:1231:43: [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 size = 2*sizeof(u32) + sizeof(u16) + strlen(name);
data/diod-1.0.24/libnpfs/np.c:1261: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).
int size = sizeof(u32) + 2 + strlen(name) + sizeof(u32) + sizeof(u32);
data/diod-1.0.24/libnpfs/np.c:1294: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).
int size = sizeof(u32) + sizeof(u16) + strlen(oldname)
data/diod-1.0.24/libnpfs/np.c:1295:34: [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).
+ sizeof(u32) + sizeof(u16) + strlen(newname);
data/diod-1.0.24/libnpfs/np.c:1327: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).
int size = sizeof(u32) + sizeof(u16) + strlen(name) + sizeof(u32);
data/diod-1.0.24/libnpfs/np.c:1688: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).
+ sizeof(u16) + strlen(name);
data/diod-1.0.24/libnpfs/npfs.h:245:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int (*read)(Npfid *fid, u64 offset, u32 count, u8 *data);
data/diod-1.0.24/libnpfs/npfs.h:306:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
Npfcall* (*read)(Npfid *fid, u64 offset, u32 count, Npreq *req);
data/diod-1.0.24/libnpfs/npstring.c:99: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).
int slen = s ? strlen (s) : 0;
data/diod-1.0.24/libnpfs/npstring.c:142: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).
int n = strlen (s);
data/diod-1.0.24/tests/kern/dbench/child.c:208:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
line[strlen(line)-1] = 0;
data/diod-1.0.24/tests/kern/dbench/dbench.c:321: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(100*1000);
data/diod-1.0.24/tests/kern/dbench/fileio.c:622: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(usec);
data/diod-1.0.24/tests/kern/dbench/io.c:132:2: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(ftable[i].fd, buf, size);
data/diod-1.0.24/tests/kern/dbench/snprintf.c:365: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).
max = strlen(strvalue);
data/diod-1.0.24/tests/kern/dbench/sockio.c:90: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).
do_packets(child, 39+2+strlen(fname)*2+2, 39);
data/diod-1.0.24/tests/kern/dbench/sockio.c:97: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).
do_packets(child, 39+2+strlen(dname)*2+2, 39);
data/diod-1.0.24/tests/kern/dbench/sockio.c:104: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).
do_packets(child, 39+2+strlen(fname)*2+2, 39);
data/diod-1.0.24/tests/kern/dbench/sockio.c:116: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).
do_packets(child, 70+2+strlen(fname)*2+2, 39+12*4);
data/diod-1.0.24/tests/kern/dbench/sockio.c:155:34: [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).
do_packets(child, 39+8+2*strlen(old)+2*strlen(new), 39);
data/diod-1.0.24/tests/kern/dbench/sockio.c:155: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).
do_packets(child, 39+8+2*strlen(old)+2*strlen(new), 39);
data/diod-1.0.24/tests/kern/dbench/sockio.c:172:35: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
do_packets(child, 39+16+2*strlen(fname), 39+32);
data/diod-1.0.24/tests/kern/dbench/sockio.c:199:33: [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).
do_packets(child, 39+20+strlen(fname)*2, 39+90*count);
data/diod-1.0.24/tests/kern/dbench/sockio.c:249: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(usec);
data/diod-1.0.24/tests/kern/dbench/util.c:81:7: [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).
ls = strlen(s);
data/diod-1.0.24/tests/kern/dbench/util.c:82:7: [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).
lp = strlen(pattern);
data/diod-1.0.24/tests/kern/dbench/util.c:83:7: [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).
li = strlen(insert);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:303:2: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(0);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:527:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(str);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:929: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).
else if (strlen(buf1) == 0)
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:931: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).
else if (strlen(buf2) == 0)
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1159: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).
else if (strlen(buf1) == 0)
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1161: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).
else if (strlen(buf2) == 0)
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1237:30: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (lead_str != NULL && x+strlen(p->name)>=WIDTH-5)
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1831:8: [1] (free) memalign:
On some systems (though not Linux-based systems) an attempt to free()
results from memalign() may fail. This may, on a few systems, be
exploitable. Also note that memalign() may not check that the boundary
parameter is correct (CWE-676). Use posix_memalign instead (defined in
POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
malloc()'s alignment may be sufficient.
buf = memalign(diob.d_mem, len);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1832:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
e = read(fd, buf, len) < 0 ? errno : 0;
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:1916:8: [1] (free) memalign:
On some systems (though not Linux-based systems) an attempt to free()
results from memalign() may fail. This may, on a few systems, be
exploitable. Also note that memalign() may not check that the boundary
parameter is correct (CWE-676). Use posix_memalign instead (defined in
POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
malloc()'s alignment may be sufficient.
buf = memalign(diob.d_mem, len);
data/diod-1.0.24/tests/kern/fsstress/fsstress.c:2247:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
e = read(fd, buf, len) < 0 ? errno : 0;
data/diod-1.0.24/tests/kern/fstest/fstest.c:602:2: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(umsk);
data/diod-1.0.24/tests/kern/fsx/fsx.c:163:26: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define fsxread(a,b,c,d) read(a,b,c)
data/diod-1.0.24/tests/kern/fsx/fsx.c:1290:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(fd, buf, len);
data/diod-1.0.24/tests/kern/fsx/fsx.c:1466:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(goodfile, optarg, sizeof(goodfile));
data/diod-1.0.24/tests/kern/fsx/fsx.c:1467:4: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(goodfile, "/");
data/diod-1.0.24/tests/kern/fsx/fsx.c:1468:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(logfile, optarg, sizeof(logfile));
data/diod-1.0.24/tests/kern/fsx/fsx.c:1469:4: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(logfile, "/");
data/diod-1.0.24/tests/kern/fsx/fsx.c:1537:2: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings.
strncat(goodfile, fname, 256);
data/diod-1.0.24/tests/kern/fsx/fsx.c:1544:2: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings.
strncat(logfile, fname, 256);
data/diod-1.0.24/tests/kern/postmark/postmark.c:774:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd,read_buffer,read_block_size);
data/diod-1.0.24/tests/kern/postmark/postmark.c:776:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd,read_buffer,i);
data/diod-1.0.24/tests/kern/postmark/postmark.c:1145: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 (param && (len=strlen(param))>0) /* if a command is specified... */
data/diod-1.0.24/tests/kern/postmark/postmark.c:1171: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).
buffer[strlen(buffer)-1]='\0'; /* delete final CR */
data/diod-1.0.24/tests/kern/postmark/postmark.c:1190: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).
system((strlen(buffer)>1)?buffer+1:getenv("SHELL"));
data/diod-1.0.24/tests/kern/postmark/postmark.c:1195: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).
len=strlen(command_list[i].name)))
data/diod-1.0.24/tests/kern/postmark/postmark.c:1198: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).
(((int)strlen(buffer)>len)?buffer+len+1:NULL);
data/diod-1.0.24/tests/kern/postmark/postmark.c:1223: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).
buffer[strlen(buffer)-1]='\0'; /* delete final CR */
data/diod-1.0.24/tests/kern/tcreate.c:19:5: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(0);
data/diod-1.0.24/tests/kern/tsuppgrp.c:41: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).
snprintf (buf+strlen(buf), sizeof(buf)-strlen(buf), "%d ", g[i]);
data/diod-1.0.24/tests/kern/tsuppgrp.c:41: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).
snprintf (buf+strlen(buf), sizeof(buf)-strlen(buf), "%d ", g[i]);
data/diod-1.0.24/tests/misc/tsuppgrp.c:42: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).
snprintf (buf+strlen(buf), sizeof(buf)-strlen(buf), "%d ", g[i]);
data/diod-1.0.24/tests/misc/tsuppgrp.c:42: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).
snprintf (buf+strlen(buf), sizeof(buf)-strlen(buf), "%d ", g[i]);
data/diod-1.0.24/tests/user/tsetxattr.c:73: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).
if (npc_setxattr (root, path, attr, value, strlen (value), flags) < 0)
data/diod-1.0.24/tests/user/twrite.c:39:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((n = read (fd, buf, sizeof (buf))) > 0) {
data/diod-1.0.24/utils/diodls.c:226: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).
(int)strlen (mtime) - 13, mtime + 4,
data/diod-1.0.24/utils/diodmount.c:286: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).
int len = strlen (h) + (p ? strlen (p) : 0) + 1;
data/diod-1.0.24/utils/diodmount.c:286: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).
int len = strlen (h) + (p ? strlen (p) : 0) + 1;
data/diod-1.0.24/utils/diodmount.c:338:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (strlen (host) == 0)
data/diod-1.0.24/utils/diodmount.c:340: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 (!aname || strlen (aname) == 0)
data/diod-1.0.24/utils/diodmount.c:626:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (strlen (host) == 0)
data/diod-1.0.24/utils/diodmount.c:628: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 ((!file || strlen (file) == 0))
data/diod-1.0.24/utils/dtop.c:318:43: [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).
mvwprintw (win, y++, 55, "%*s", (int)(strlen (ts) - 1), ts);
data/diod-1.0.24/utils/dtop.c:335:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read, write, clunk, remove);
data/diod-1.0.24/utils/dtop.c:581: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).
s[strlen (s) - 1] = '\0';
data/diod-1.0.24/utils/dtop.c:743: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).
char *p = s + strlen (s);
data/diod-1.0.24/utils/dtop.c:967:9: [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 ((useconds_t)(sp->poll_sec * 1E6));
data/diod-1.0.24/utils/opt.c:89: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).
strsize += strlen (item) + 1;
data/diod-1.0.24/utils/opt.c:96: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).
n = strlen (s);
data/diod-1.0.24/utils/opt.c:114:28: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int n = p ? p - item : strlen (item);
data/diod-1.0.24/utils/opt.c:116: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).
int m = q ? q - key : strlen (key);
data/diod-1.0.24/utils/opt.c:156:28: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return p ? p + 1 : s + strlen (s);
ANALYSIS SUMMARY:
Hits = 558
Lines analyzed = 42763 in approximately 1.12 seconds (38341 lines/second)
Physical Source Lines of Code (SLOC) = 33136
Hits@level = [0] 527 [1] 137 [2] 246 [3] 81 [4] 85 [5] 9
Hits@level+ = [0+] 1085 [1+] 558 [2+] 421 [3+] 175 [4+] 94 [5+] 9
Hits/KSLOC@level+ = [0+] 32.7438 [1+] 16.8397 [2+] 12.7052 [3+] 5.28127 [4+] 2.83679 [5+] 0.271608
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.