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/maildir-utils-1.4.13/contrib/gmime-test.c
Examining data/maildir-utils-1.4.13/guile/mu-guile-message.c
Examining data/maildir-utils-1.4.13/guile/mu-guile-message.h
Examining data/maildir-utils-1.4.13/guile/mu-guile.c
Examining data/maildir-utils-1.4.13/guile/mu-guile.h
Examining data/maildir-utils-1.4.13/guile/tests/test-mu-guile.c
Examining data/maildir-utils-1.4.13/lib/mu-bookmarks.c
Examining data/maildir-utils-1.4.13/lib/mu-bookmarks.h
Examining data/maildir-utils-1.4.13/lib/mu-contacts.cc
Examining data/maildir-utils-1.4.13/lib/mu-container.c
Examining data/maildir-utils-1.4.13/lib/mu-container.h
Examining data/maildir-utils-1.4.13/lib/mu-flags.c
Examining data/maildir-utils-1.4.13/lib/mu-flags.h
Examining data/maildir-utils-1.4.13/lib/mu-index.c
Examining data/maildir-utils-1.4.13/lib/mu-index.h
Examining data/maildir-utils-1.4.13/lib/mu-maildir.c
Examining data/maildir-utils-1.4.13/lib/mu-maildir.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-crypto.c
Examining data/maildir-utils-1.4.13/lib/mu-msg-doc.cc
Examining data/maildir-utils-1.4.13/lib/mu-msg-doc.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-fields.c
Examining data/maildir-utils-1.4.13/lib/mu-msg-fields.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-file.c
Examining data/maildir-utils-1.4.13/lib/mu-msg-file.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-iter.cc
Examining data/maildir-utils-1.4.13/lib/mu-msg-iter.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-json.c
Examining data/maildir-utils-1.4.13/lib/mu-msg-part.c
Examining data/maildir-utils-1.4.13/lib/mu-msg-part.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-prio.c
Examining data/maildir-utils-1.4.13/lib/mu-msg-prio.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-priv.h
Examining data/maildir-utils-1.4.13/lib/mu-msg-sexp.c
Examining data/maildir-utils-1.4.13/lib/mu-msg.c
Examining data/maildir-utils-1.4.13/lib/mu-msg.h
Examining data/maildir-utils-1.4.13/lib/mu-query.cc
Examining data/maildir-utils-1.4.13/lib/mu-query.h
Examining data/maildir-utils-1.4.13/lib/mu-runtime.cc
Examining data/maildir-utils-1.4.13/lib/mu-runtime.h
Examining data/maildir-utils-1.4.13/lib/mu-script.c
Examining data/maildir-utils-1.4.13/lib/mu-script.h
Examining data/maildir-utils-1.4.13/lib/mu-store.cc
Examining data/maildir-utils-1.4.13/lib/mu-threader.c
Examining data/maildir-utils-1.4.13/lib/mu-threader.h
Examining data/maildir-utils-1.4.13/lib/query/mu-parser.cc
Examining data/maildir-utils-1.4.13/lib/query/mu-tokenizer.cc
Examining data/maildir-utils-1.4.13/lib/query/mu-xapian.cc
Examining data/maildir-utils-1.4.13/lib/query/parse.cc
Examining data/maildir-utils-1.4.13/lib/query/test-parser.cc
Examining data/maildir-utils-1.4.13/lib/query/test-tokenizer.cc
Examining data/maildir-utils-1.4.13/lib/query/tokenize.cc
Examining data/maildir-utils-1.4.13/lib/test-mu-common.c
Examining data/maildir-utils-1.4.13/lib/test-mu-common.h
Examining data/maildir-utils-1.4.13/lib/test-mu-contacts.cc
Examining data/maildir-utils-1.4.13/lib/test-mu-container.c
Examining data/maildir-utils-1.4.13/lib/test-mu-date.c
Examining data/maildir-utils-1.4.13/lib/test-mu-flags.c
Examining data/maildir-utils-1.4.13/lib/test-mu-maildir.c
Examining data/maildir-utils-1.4.13/lib/test-mu-msg-fields.c
Examining data/maildir-utils-1.4.13/lib/test-mu-msg.c
Examining data/maildir-utils-1.4.13/lib/test-mu-store.c
Examining data/maildir-utils-1.4.13/lib/utils/mu-command-parser.cc
Examining data/maildir-utils-1.4.13/lib/utils/mu-date.c
Examining data/maildir-utils-1.4.13/lib/utils/mu-date.h
Examining data/maildir-utils-1.4.13/lib/utils/mu-log.c
Examining data/maildir-utils-1.4.13/lib/utils/mu-log.h
Examining data/maildir-utils-1.4.13/lib/utils/mu-sexp-parser.cc
Examining data/maildir-utils-1.4.13/lib/utils/mu-str.c
Examining data/maildir-utils-1.4.13/lib/utils/mu-str.h
Examining data/maildir-utils-1.4.13/lib/utils/mu-util.c
Examining data/maildir-utils-1.4.13/lib/utils/mu-util.h
Examining data/maildir-utils-1.4.13/lib/utils/mu-utils.cc
Examining data/maildir-utils-1.4.13/lib/utils/test-command-parser.cc
Examining data/maildir-utils-1.4.13/lib/utils/test-mu-str.c
Examining data/maildir-utils-1.4.13/lib/utils/test-mu-util.c
Examining data/maildir-utils-1.4.13/lib/utils/test-sexp-parser.cc
Examining data/maildir-utils-1.4.13/lib/utils/test-utils.cc
Examining data/maildir-utils-1.4.13/mu/mu-cmd-cfind.c
Examining data/maildir-utils-1.4.13/mu/mu-cmd-extract.c
Examining data/maildir-utils-1.4.13/mu/mu-cmd-find.c
Examining data/maildir-utils-1.4.13/mu/mu-cmd-index.c
Examining data/maildir-utils-1.4.13/mu/mu-cmd-script.c
Examining data/maildir-utils-1.4.13/mu/mu-cmd-server.cc
Examining data/maildir-utils-1.4.13/mu/mu-cmd.c
Examining data/maildir-utils-1.4.13/mu/mu-cmd.h
Examining data/maildir-utils-1.4.13/mu/mu-config.c
Examining data/maildir-utils-1.4.13/mu/mu-config.h
Examining data/maildir-utils-1.4.13/mu/mu.cc
Examining data/maildir-utils-1.4.13/mu/test-mu-cmd-cfind.c
Examining data/maildir-utils-1.4.13/mu/test-mu-cmd.c
Examining data/maildir-utils-1.4.13/mu/test-mu-query.c
Examining data/maildir-utils-1.4.13/mu/test-mu-runtime.c
Examining data/maildir-utils-1.4.13/mu/test-mu-threads.c
Examining data/maildir-utils-1.4.13/toys/msg2pdf/msg2pdf.c
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-attach-view.c
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-attach-view.h
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-body-view.c
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-body-view.h
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-header-view.c
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-header-view.h
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-view.c
Examining data/maildir-utils-1.4.13/toys/mug/mu-msg-view.h
Examining data/maildir-utils-1.4.13/toys/mug/mu-widget-util.c
Examining data/maildir-utils-1.4.13/toys/mug/mu-widget-util.h
Examining data/maildir-utils-1.4.13/toys/mug/mug-msg-list-view.c
Examining data/maildir-utils-1.4.13/toys/mug/mug-msg-list-view.h
Examining data/maildir-utils-1.4.13/toys/mug/mug-msg-view.c
Examining data/maildir-utils-1.4.13/toys/mug/mug-msg-view.h
Examining data/maildir-utils-1.4.13/toys/mug/mug-query-bar.c
Examining data/maildir-utils-1.4.13/toys/mug/mug-query-bar.h
Examining data/maildir-utils-1.4.13/toys/mug/mug-shortcuts.c
Examining data/maildir-utils-1.4.13/toys/mug/mug-shortcuts.h
Examining data/maildir-utils-1.4.13/toys/mug/mug.c
FINAL RESULTS:
data/maildir-utils-1.4.13/guile/tests/test-mu-guile.c:87:11: [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.
result = system (cmdline);
data/maildir-utils-1.4.13/lib/mu-index.c:277:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (path, R_OK) != 0) {
data/maildir-utils-1.4.13/lib/mu-index.c:424:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (path, R_OK) != 0) {
data/maildir-utils-1.4.13/lib/mu-maildir.c:225:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (G_UNLIKELY(access(fullpath, R_OK) != 0)) {
data/maildir-utils-1.4.13/lib/mu-maildir.c:293:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (fullpath, F_OK) == 0)
data/maildir-utils-1.4.13/lib/mu-maildir.c:406: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 (fullpath, fp);
data/maildir-utils-1.4.13/lib/mu-maildir.c:858:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (src, R_OK) != 0)
data/maildir-utils-1.4.13/lib/mu-maildir.c:862:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (dst, F_OK) != 0)
data/maildir-utils-1.4.13/lib/mu-maildir.c:882:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (dst, F_OK) != 0)
data/maildir-utils-1.4.13/lib/mu-maildir.c:886:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (src, F_OK) == 0)
data/maildir-utils-1.4.13/lib/mu-msg-file.c:82:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (path, R_OK) != 0) {
data/maildir-utils-1.4.13/lib/mu-msg-iter.cc:214:14: [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.
readable = (access (path.c_str(), R_OK) == 0) ? TRUE : FALSE;
data/maildir-utils-1.4.13/lib/mu-msg-part.c:762:22: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (use_existing && access (fullpath, F_OK) == 0)
data/maildir-utils-1.4.13/lib/mu-msg.c:829:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access (mu_msg_get_path (self), R_OK) == 0 ? TRUE : FALSE;
data/maildir-utils-1.4.13/lib/mu-script.c:324:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (mu_script_info_path (msi), R_OK) != 0) {
data/maildir-utils-1.4.13/lib/utils/mu-sexp-parser.cc:27:23: [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, 0))) static Mu::Error
data/maildir-utils-1.4.13/lib/utils/mu-util.c:105:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (dir, F_OK) != 0)
data/maildir-utils-1.4.13/lib/utils/mu-util.c:157:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (path, mode) != 0) {
data/maildir-utils-1.4.13/lib/utils/mu-util.c:207:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
(access (path, W_OK|R_OK) != 0)) {
data/maildir-utils-1.4.13/lib/utils/mu-util.c:249:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (path, R_OK) == 0)
data/maildir-utils-1.4.13/lib/utils/mu-util.c:431:23: [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, 0))) static gboolean
data/maildir-utils-1.4.13/lib/utils/mu-util.c:487:9: [4] (misc) getpass:
This function is obsolete and not portable. It was in SUSv2 but removed by
POSIX.2. What it does exactly varies considerably between systems,
particularly in where its prompt is displayed and where it gets its data
(e.g., /dev/tty, stdin, stderr, etc.). In addition, some implementations
overflow buffers. (CWE-676, CWE-120, CWE-20). Make the specific calls to do
exactly what you want. If you continue to use it, or write your own, be
sure to zero the password as soon as possible to avoid leaving the
cleartext password visible in the process' address space.
pass = getpass (prompt); /* returns static mem, don't free */
data/maildir-utils-1.4.13/lib/utils/test-mu-util.c:84:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access ("/tmp", F_OK))
data/maildir-utils-1.4.13/lib/utils/test-mu-util.c:108:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (mdir, F_OK) == 0)
data/maildir-utils-1.4.13/mu/mu-cmd.c:307:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (cmd_add && access(path, R_OK) != 0) {
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:551:12: [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.
g_assert (access (path, F_OK) == 0);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:747:12: [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.
g_assert (access (dir, F_OK) == 0);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:752:12: [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.
g_assert (access (dir, F_OK) == 0);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:757:12: [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.
g_assert (access (dir, F_OK) == 0);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:777:7: [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 (gpg, X_OK) != 0)
data/maildir-utils-1.4.13/toys/msg2pdf/msg2pdf.c:284:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access (argv[1], R_OK) != 0) {
data/maildir-utils-1.4.13/toys/mug/mug-msg-view.c:121:7: [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 (msgpath, R_OK) == 0) {
data/maildir-utils-1.4.13/lib/mu-maildir.c:777:5: [3] (random) g_random_int:
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.
g_random_int(),
data/maildir-utils-1.4.13/lib/mu-msg-file.c:106:7: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
if (!realpath (path, self->_path)) {
data/maildir-utils-1.4.13/lib/test-mu-common.c:44:3: [3] (buffer) g_get_tmp_dir:
This function is synonymous with 'getenv("TMP")';it returns untrustable
input if the environment can beset by an attacker. It 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.
g_get_tmp_dir(),
data/maildir-utils-1.4.13/lib/test-mu-common.c:48:8: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
(int)random()*getpid()*(int)time(NULL));
data/maildir-utils-1.4.13/lib/test-mu-common.c:62:10: [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.
oldtz = getenv ("TZ");
data/maildir-utils-1.4.13/lib/utils/mu-util.c:109:6: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
if (realpath (dir, resolved) == NULL) {
data/maildir-utils-1.4.13/lib/utils/mu-util.c:139:5: [3] (buffer) g_get_tmp_dir:
This function is synonymous with 'getenv("TMP")';it returns untrustable
input if the environment can beset by an attacker. It 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.
g_get_tmp_dir(), G_DIR_SEPARATOR,
data/maildir-utils-1.4.13/lib/utils/mu-util.c:183:9: [3] (buffer) g_get_home_dir:
This function is synonymous with 'getenv("HOME")';it returns untrustable
input if the environment can beset by an attacker. It 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.
home = g_get_home_dir();
data/maildir-utils-1.4.13/lib/utils/test-mu-util.c:41:9: [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.
getenv("HOME"), G_DIR_SEPARATOR);
data/maildir-utils-1.4.13/lib/utils/test-mu-util.c:65:9: [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.
getenv("HOME"), G_DIR_SEPARATOR);
data/maildir-utils-1.4.13/lib/utils/test-mu-util.c:105:5: [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.
getenv("HOME"), G_DIR_SEPARATOR);
data/maildir-utils-1.4.13/toys/msg2pdf/msg2pdf.c:66:32: [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.
G_DIR_SEPARATOR, (unsigned)random());
data/maildir-utils-1.4.13/contrib/gmime-test.c:122: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[512];
data/maildir-utils-1.4.13/contrib/gmime-test.c:229:9: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
file = fopen (path, "r");
data/maildir-utils-1.4.13/lib/mu-container.c:547: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 segm[16];
data/maildir-utils-1.4.13/lib/mu-container.c:649: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 frmt[16];
data/maildir-utils-1.4.13/lib/mu-flags.c:125: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 str[sizeof(FLAG_INFO) + 1];
data/maildir-utils-1.4.13/lib/mu-msg-file.c:123:9: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
file = fopen (path, "r");
data/maildir-utils-1.4.13/lib/mu-msg-json.c:328:16: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
char *name, *tmpfile;
data/maildir-utils-1.4.13/lib/mu-msg-json.c:345:41: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
add_string_member (pinfo->bob, "temp", tmpfile);
data/maildir-utils-1.4.13/lib/mu-msg-json.c:357:10: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
g_free (tmpfile);
data/maildir-utils-1.4.13/lib/mu-msg-priv.h:43:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char _path [PATH_MAX + 1];
data/maildir-utils-1.4.13/lib/mu-msg-priv.h:44:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char _maildir [PATH_MAX + 1];
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:280:14: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
char *tmp, *tmpfile;
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:294:9: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
return tmpfile;
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:394:9: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
char *tmpfile, *cidesc, *verdict;
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:419:4: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
tmpfile ? " :temp" : "", tmpfile ? tmpfile : "",
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:419:29: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
tmpfile ? " :temp" : "", tmpfile ? tmpfile : "",
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:419:39: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
tmpfile ? " :temp" : "", tmpfile ? tmpfile : "",
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:428:10: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
g_free (tmpfile);
data/maildir-utils-1.4.13/lib/mu-store.cc:218: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 uid_term[1 + 16 + 1] = {'\0'};
data/maildir-utils-1.4.13/lib/mu-store.cc:998: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 ctype[MU_STORE_MAX_TERM_LENGTH + 1];
data/maildir-utils-1.4.13/lib/mu-store.cc:1247: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 thread_id[16+1];
data/maildir-utils-1.4.13/lib/mu-store.cc:1411: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 tbuf[64];
data/maildir-utils-1.4.13/lib/mu-threader.c:159: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 fake[32];
data/maildir-utils-1.4.13/lib/utils/mu-command-parser.cc:159: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).
return ::atoi(it->value.c_str());
data/maildir-utils-1.4.13/lib/utils/mu-date.c:32: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 buf[128];
data/maildir-utils-1.4.13/lib/utils/mu-date.c:56:4: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy (buf, "<error>");
data/maildir-utils-1.4.13/lib/utils/mu-log.c:191: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 (logfile, O_WRONLY|O_CREAT|O_APPEND, 00600);
data/maildir-utils-1.4.13/lib/utils/mu-log.c:253: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 timebuf [22];
data/maildir-utils-1.4.13/lib/utils/mu-str.c:38:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static char buf[32];
data/maildir-utils-1.4.13/lib/utils/mu-str.c:137: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 sep[4] = { '\0', '\0', '\0', '\0' };
data/maildir-utils-1.4.13/lib/utils/mu-str.c:157: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 sep[4] = { '\0', '\0', '\0', '\0' };
data/maildir-utils-1.4.13/lib/utils/mu-str.c:298: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 buf[PATH_MAX + 1];
data/maildir-utils-1.4.13/lib/utils/mu-util.c:96: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 resolved[PATH_MAX + 1];
data/maildir-utils-1.4.13/lib/utils/mu-util.c:136: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 cachedir [PATH_MAX];
data/maildir-utils-1.4.13/lib/utils/mu-util.c:234: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).
return open (path, O_WRONLY|O_CREAT|O_TRUNC, mode);
data/maildir-utils-1.4.13/lib/utils/mu-util.c:236: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).
return open (path, O_WRONLY|O_CREAT|O_EXCL, mode);
data/maildir-utils-1.4.13/lib/utils/mu-utils.cc:222: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[sizeof(InternalDateMax)];
data/maildir-utils-1.4.13/lib/utils/mu-utils.cc:400: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[sizeof(SizeMax)];
data/maildir-utils-1.4.13/mu/mu-cmd-cfind.c:357:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char datebuf[32];
data/maildir-utils-1.4.13/mu/mu-cmd-find.c:327: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 buf[80];
data/maildir-utils-1.4.13/mu/mu-cmd-index.c:106:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char output[120];
data/maildir-utils-1.4.13/mu/mu-cmd-server.cc:93: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 cookie[16];
data/maildir-utils-1.4.13/mu/mu-cmd-server.cc:114:18: [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.
lenlen = sprintf(cookie + 1, "%x",
data/maildir-utils-1.4.13/toys/mug/mu-msg-attach-view.c:241: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 ctype[128];
data/maildir-utils-1.4.13/guile/mu-guile.c:46: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).
return scm_from_stringn (str, strlen(str), "UTF-8",
data/maildir-utils-1.4.13/lib/mu-flags.c:188: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).
custom = g_new0 (char, strlen(str) + 1);
data/maildir-utils-1.4.13/lib/mu-maildir.c:258: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).
len = path ? strlen (path) : 0;
data/maildir-utils-1.4.13/lib/mu-maildir.c:405: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).
fullpath = g_newa (char, strlen(fp) + 1);
data/maildir-utils-1.4.13/lib/mu-maildir.c:576: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).
if (mypath[strlen(mypath)-1] == G_DIR_SEPARATOR)
data/maildir-utils-1.4.13/lib/mu-maildir.c:577: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).
mypath[strlen(mypath)-1] = '\0';
data/maildir-utils-1.4.13/lib/mu-maildir.c:766: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).
mdir[strlen(mdir) - 4] = '\0';
data/maildir-utils-1.4.13/lib/mu-maildir.c:805:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
for (cur = &mfile[strlen(mfile)-1]; cur > mfile; --cur) {
data/maildir-utils-1.4.13/lib/mu-msg-file.c:113:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (self->_maildir, mdir ? mdir : "", PATH_MAX);
data/maildir-utils-1.4.13/lib/mu-msg-file.c:653: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).
if (msgid && strlen(msgid) < MU_STORE_MAX_TERM_LENGTH) {
data/maildir-utils-1.4.13/lib/mu-msg-part.c:261: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).
gstr = g_string_sized_new (strlen (fname));
data/maildir-utils-1.4.13/lib/mu-msg-part.c:738:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (write (fd, str, strlen(str)) == -1) {
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:54: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).
if (!str || strlen(str) == 0)
data/maildir-utils-1.4.13/lib/mu-msg-sexp.c:76: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).
if (!str || strlen(str) == 0)
data/maildir-utils-1.4.13/lib/mu-msg.c:879: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).
rootmaildir[strlen(rootmaildir) -
data/maildir-utils-1.4.13/lib/mu-msg.c:880: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).
strlen (mu_msg_get_maildir(msg))] = '\0';
data/maildir-utils-1.4.13/lib/mu-script.c:213: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).
oneline = g_strdup (line + strlen (prefix));
data/maildir-utils-1.4.13/lib/mu-script.c:219: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).
line + strlen(prefix));
data/maildir-utils-1.4.13/lib/mu-script.c:269: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).
msi->_name[strlen(msi->_name) - strlen(ext)] = '\0';
data/maildir-utils-1.4.13/lib/mu-script.c:269: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).
msi->_name[strlen(msi->_name) - strlen(ext)] = '\0';
data/maildir-utils-1.4.13/lib/utils/mu-date.c:58:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (buf, conv, sizeof(buf)-1);
data/maildir-utils-1.4.13/lib/utils/mu-log.c:261: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).
if (write (MU_LOG->_fd, timebuf, strlen (timebuf)) < 0)
data/maildir-utils-1.4.13/lib/utils/mu-log.c:265: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).
if (write (MU_LOG->_fd, mylevel, strlen (mylevel)) < 0)
data/maildir-utils-1.4.13/lib/utils/mu-log.c:268: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).
if (write (MU_LOG->_fd, msg, strlen (msg)) < 0)
data/maildir-utils-1.4.13/lib/utils/mu-log.c:271: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 (write (MU_LOG->_fd, "\n", strlen ("\n")) < 0)
data/maildir-utils-1.4.13/lib/utils/mu-str.c:42:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (buf, tmp, sizeof(buf));
data/maildir-utils-1.4.13/lib/utils/mu-str.c:68:26: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
summary = g_new (gchar, strlen(str) + 1);
data/maildir-utils-1.4.13/lib/utils/mu-str.c:110: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).
gstr = g_string_sized_new (2 * strlen (str));
data/maildir-utils-1.4.13/lib/utils/mu-str.c:115: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).
cur += strlen (substr) - 1;
data/maildir-utils-1.4.13/lib/utils/mu-str.c:195: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).
u != strlen (strings); ++u) {
data/maildir-utils-1.4.13/lib/utils/mu-str.c:317: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).
tmp = g_string_sized_new (2 * strlen(str));
data/maildir-utils-1.4.13/lib/utils/mu-util.c:246:44: [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 (g_ascii_strncasecmp ("file://", path, strlen("file://")) == 0)
data/maildir-utils-1.4.13/lib/utils/mu-utils.cc:84: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).
gstr = g_string_sized_new (strlen (norm));
data/maildir-utils-1.4.13/mu/mu-cmd-cfind.c:101: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).
s = g_new0 (char, strlen(str) + 1);
data/maildir-utils-1.4.13/mu/mu-cmd-extract.c:116: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).
pattern[strlen(pattern)-1] == '$' ? "" : "$");
data/maildir-utils-1.4.13/mu/mu-cmd-find.c:83:6: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
strlen(fieldstr) == 1)
data/maildir-utils-1.4.13/mu/mu-cmd-find.c:335:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (buf, str, sizeof(buf)-1);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:609: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(output);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:646: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(output);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:683: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(output);
data/maildir-utils-1.4.13/mu/test-mu-cmd.c:716: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(output);
ANALYSIS SUMMARY:
Hits = 129
Lines analyzed = 34483 in approximately 0.79 seconds (43735 lines/second)
Physical Source Lines of Code (SLOC) = 22053
Hits@level = [0] 4 [1] 41 [2] 44 [3] 12 [4] 32 [5] 0
Hits@level+ = [0+] 133 [1+] 129 [2+] 88 [3+] 44 [4+] 32 [5+] 0
Hits/KSLOC@level+ = [0+] 6.03093 [1+] 5.84954 [2+] 3.99039 [3+] 1.99519 [4+] 1.45105 [5+] 0
Dot directories skipped = 2 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.