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/iptux-0.7.6/src/iptux/AnalogFS.cpp
Examining data/iptux-0.7.6/src/iptux/AnalogFS.h
Examining data/iptux-0.7.6/src/iptux/Command.cpp
Examining data/iptux-0.7.6/src/iptux/Command.h
Examining data/iptux-0.7.6/src/iptux/CoreThread.cpp
Examining data/iptux-0.7.6/src/iptux/CoreThread.h
Examining data/iptux-0.7.6/src/iptux/DataSettings.cpp
Examining data/iptux-0.7.6/src/iptux/DataSettings.h
Examining data/iptux-0.7.6/src/iptux/DetectPal.cpp
Examining data/iptux-0.7.6/src/iptux/DetectPal.h
Examining data/iptux-0.7.6/src/iptux/DialogBase.cpp
Examining data/iptux-0.7.6/src/iptux/DialogBase.h
Examining data/iptux-0.7.6/src/iptux/DialogGroup.cpp
Examining data/iptux-0.7.6/src/iptux/DialogGroup.h
Examining data/iptux-0.7.6/src/iptux/DialogPeer.cpp
Examining data/iptux-0.7.6/src/iptux/DialogPeer.h
Examining data/iptux-0.7.6/src/iptux/HelpDialog.cpp
Examining data/iptux-0.7.6/src/iptux/HelpDialog.h
Examining data/iptux-0.7.6/src/iptux/IptuxConfig.cpp
Examining data/iptux-0.7.6/src/iptux/IptuxConfig.h
Examining data/iptux-0.7.6/src/iptux/IptuxConfigTest.cpp
Examining data/iptux-0.7.6/src/iptux/LogSystem.cpp
Examining data/iptux-0.7.6/src/iptux/LogSystem.h
Examining data/iptux-0.7.6/src/iptux/MainWindow.cpp
Examining data/iptux-0.7.6/src/iptux/MainWindow.h
Examining data/iptux-0.7.6/src/iptux/ProgramData.cpp
Examining data/iptux-0.7.6/src/iptux/ProgramData.h
Examining data/iptux-0.7.6/src/iptux/RecvFile.cpp
Examining data/iptux-0.7.6/src/iptux/RecvFile.h
Examining data/iptux-0.7.6/src/iptux/RecvFileData.cpp
Examining data/iptux-0.7.6/src/iptux/RecvFileData.h
Examining data/iptux-0.7.6/src/iptux/RevisePal.cpp
Examining data/iptux-0.7.6/src/iptux/RevisePal.h
Examining data/iptux-0.7.6/src/iptux/SendFile.cpp
Examining data/iptux-0.7.6/src/iptux/SendFile.h
Examining data/iptux-0.7.6/src/iptux/SendFileData.cpp
Examining data/iptux-0.7.6/src/iptux/SendFileData.h
Examining data/iptux-0.7.6/src/iptux/ShareFile.cpp
Examining data/iptux-0.7.6/src/iptux/ShareFile.h
Examining data/iptux-0.7.6/src/iptux/SoundSystem.cpp
Examining data/iptux-0.7.6/src/iptux/SoundSystem.h
Examining data/iptux-0.7.6/src/iptux/StatusIcon.cpp
Examining data/iptux-0.7.6/src/iptux/StatusIcon.h
Examining data/iptux-0.7.6/src/iptux/TcpData.cpp
Examining data/iptux-0.7.6/src/iptux/TcpData.h
Examining data/iptux-0.7.6/src/iptux/TestMain.cpp
Examining data/iptux-0.7.6/src/iptux/UdpData.cpp
Examining data/iptux-0.7.6/src/iptux/UdpData.h
Examining data/iptux-0.7.6/src/iptux/UtilsTest.cpp
Examining data/iptux-0.7.6/src/iptux/WindowConfig.cpp
Examining data/iptux-0.7.6/src/iptux/WindowConfig.h
Examining data/iptux-0.7.6/src/iptux/callback.cpp
Examining data/iptux-0.7.6/src/iptux/callback.h
Examining data/iptux-0.7.6/src/iptux/deplib.h
Examining data/iptux-0.7.6/src/iptux/dialog.cpp
Examining data/iptux-0.7.6/src/iptux/dialog.h
Examining data/iptux-0.7.6/src/iptux/global.h
Examining data/iptux-0.7.6/src/iptux/ipmsg.h
Examining data/iptux-0.7.6/src/iptux/mess.cpp
Examining data/iptux-0.7.6/src/iptux/mess.h
Examining data/iptux-0.7.6/src/iptux/output.cpp
Examining data/iptux-0.7.6/src/iptux/output.h
Examining data/iptux-0.7.6/src/iptux/support.cpp
Examining data/iptux-0.7.6/src/iptux/support.h
Examining data/iptux-0.7.6/src/iptux/utils.cpp
Examining data/iptux-0.7.6/src/iptux/utils.h
Examining data/iptux-0.7.6/src/iptux/wrapper.cpp
Examining data/iptux-0.7.6/src/iptux/wrapper.h
Examining data/iptux-0.7.6/src/main/iptux.cpp
FINAL RESULTS:
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:78:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(tpath, path);
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:102:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(tpath, path);
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:121:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(tpath, path);
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:123: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(tpath, F_OK) == 0) return 0;
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:169: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(tpath, dir_name);
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:195:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(tpath, path);
data/iptux-0.7.6/src/iptux/Command.cpp:235:3: [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.
snprintf(packetstr, 11, "%" PRIu32, packetno);
data/iptux-0.7.6/src/iptux/Command.cpp:304:3: [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.
snprintf(attrstr, 35, "%" PRIx32 ":%" PRIx32 ":%" PRIx64, packetno, fileid,
data/iptux-0.7.6/src/iptux/Command.cpp:542:3: [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.
snprintf(ptr, MAX_UDPLEN - size, ":%" PRIu32, packetn);
data/iptux-0.7.6/src/iptux/Command.cpp:560:5: [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.
snprintf(ptr, MAX_UDPLEN - size, ":%" PRIu32, command);
data/iptux-0.7.6/src/iptux/CoreThread.cpp:224: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(path, F_OK) == 0) cmd.SendMyIcon(g_cthrd->udpsock, pal);
data/iptux-0.7.6/src/iptux/CoreThread.cpp:226: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(path, F_OK) == 0) {
data/iptux-0.7.6/src/iptux/CoreThread.cpp:954:5: [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.
snprintf(name, 9, "%" PRIx32, count++);
data/iptux-0.7.6/src/iptux/DataSettings.cpp:911:7: [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.
snprintf(path, MAX_PATHLEN, __PIXMAPS_PATH "/icon/%s", file);
data/iptux-0.7.6/src/iptux/DataSettings.cpp:912:11: [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, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/DataSettings.cpp:974:7: [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.
snprintf(path, MAX_PATHLEN, __PIXMAPS_PATH "/icon/%s", file);
data/iptux-0.7.6/src/iptux/DataSettings.cpp:975:11: [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, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1143:13: [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.
switch (sscanf(lineptr, "%s - %s //%s", buf[0], buf[1], buf[2])) {
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1229: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(pathname, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/IptuxConfigTest.cpp:14:19: [4] (tmpfile) mktemp:
Temporary file race condition (CWE-377).
char* tmpfile = mktemp(templateFname);
data/iptux-0.7.6/src/iptux/MainWindow.cpp:1630:5: [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.
snprintf(buf, MAX_BUFLEN, _("Pals Online: %" PRIu32), sum);
data/iptux-0.7.6/src/iptux/ProgramData.cpp:213:3: [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.
snprintf(pathbuf, MAX_PATHLEN, __PIXMAPS_PATH "/icon/%s", myicon.c_str());
data/iptux-0.7.6/src/iptux/ProgramData.cpp:214: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(pathbuf, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/ProgramData.cpp:223:3: [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.
snprintf(pathbuf, MAX_PATHLEN, __PIXMAPS_PATH "/icon/%s", palicon);
data/iptux-0.7.6/src/iptux/ProgramData.cpp:224: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(pathbuf, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/RevisePal.cpp:254:5: [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.
snprintf(path, MAX_PATHLEN, __PIXMAPS_PATH "/icon/%s", file);
data/iptux-0.7.6/src/iptux/RevisePal.cpp:255: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(path, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/RevisePal.cpp:258:7: [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.
snprintf(path, MAX_PATHLEN, "%s" ICON_PATH "/%" PRIx32,
data/iptux-0.7.6/src/iptux/RevisePal.cpp:382: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(pathname, F_OK) != 0) {
data/iptux-0.7.6/src/iptux/SendFile.cpp:130: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(file->filepath, F_OK) == -1) {
data/iptux-0.7.6/src/iptux/SendFile.cpp:177:13: [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(file->filepath, F_OK) == -1) {
data/iptux-0.7.6/src/iptux/SendFileData.cpp:177:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(vdirt.d_name, dirname);
data/iptux-0.7.6/src/iptux/SendFileData.cpp:225:7: [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.
snprintf(buf, MAX_SOCKLEN, "%.4" PRIx32, headsize);
data/iptux-0.7.6/src/iptux/SendFileData.cpp:257:7: [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.
snprintf(buf, MAX_SOCKLEN, "%.4" PRIx32, headsize);
data/iptux-0.7.6/src/iptux/TcpData.cpp:124:7: [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.
snprintf(path, MAX_PATHLEN, "%s" PHOTO_PATH "/%" PRIx32,
data/iptux-0.7.6/src/iptux/UdpData.cpp:712:5: [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.
snprintf(path, MAX_PATHLEN, __PIXMAPS_PATH "/icon/%s", ptr);
data/iptux-0.7.6/src/iptux/UdpData.cpp:713: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(path, F_OK) == 0) return g_strdup(ptr);
data/iptux-0.7.6/src/iptux/UdpData.cpp:745:3: [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.
snprintf(path, MAX_PATHLEN, "%s" ICON_PATH "/%" PRIx32,
data/iptux-0.7.6/src/iptux/support.cpp:91:3: [4] (shell) execlp:
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.
execlp("xdg-open", "xdg-open", url, NULL);
data/iptux-0.7.6/src/iptux/support.cpp:93:3: [4] (shell) execlp:
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.
execlp("firefox", "firefox", url, NULL);
data/iptux-0.7.6/src/iptux/support.cpp:94:3: [4] (shell) execlp:
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.
execlp("opera", "opera", url, NULL);
data/iptux-0.7.6/src/iptux/support.cpp:95:3: [4] (shell) execlp:
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.
execlp("konqueror", "konqueror", url, NULL);
data/iptux-0.7.6/src/iptux/support.cpp:96:3: [4] (shell) execlp:
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.
execlp("open", "open", url, NULL);
data/iptux-0.7.6/src/iptux/support.cpp:150: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(env, F_OK) != 0) mkdir(env, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:151:3: [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.
snprintf(path, MAX_PATHLEN, "%s" IPTUX_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:152: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:153:3: [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.
snprintf(path, MAX_PATHLEN, "%s" PIC_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:154: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:155:3: [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.
snprintf(path, MAX_PATHLEN, "%s" PHOTO_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:156: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:157:3: [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.
snprintf(path, MAX_PATHLEN, "%s" ICON_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:158: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:159:3: [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.
snprintf(path, MAX_PATHLEN, "%s" LOG_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:160: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:163: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(env, F_OK) != 0) mkdir(env, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:164:3: [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.
snprintf(path, MAX_PATHLEN, "%s" IPTUX_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:165: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:166:3: [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.
snprintf(path, MAX_PATHLEN, "%s" LOG_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:167: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:168:3: [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.
snprintf(path, MAX_PATHLEN, "%s" PHOTO_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:169: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:170:3: [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.
snprintf(path, MAX_PATHLEN, "%s" ICON_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:171: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/support.cpp:172:3: [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.
snprintf(path, MAX_PATHLEN, "%s" LOG_PATH, env);
data/iptux-0.7.6/src/iptux/support.cpp:173: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(path, F_OK) != 0) mkdir(path, 0777);
data/iptux-0.7.6/src/iptux/utils.cpp:195: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(path, F_OK) != 0) return g_strdup(path);
data/iptux-0.7.6/src/iptux/utils.cpp:203: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(buf, F_OK) != 0) break;
data/iptux-0.7.6/src/iptux/utils.cpp:370:7: [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.
if (sscanf(ptr, "%" SCNx64, &number) == 1) return number;
data/iptux-0.7.6/src/iptux/utils.cpp:386:7: [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.
if (sscanf(ptr, "%" SCNx32, &number) == 1) return number;
data/iptux-0.7.6/src/iptux/utils.cpp:402:7: [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.
if (sscanf(ptr, "%" SCNu32, &number) == 1) return number;
data/iptux-0.7.6/src/iptux/utils.cpp:554:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(filename, path);
data/iptux-0.7.6/src/iptux/utils.cpp:556:3: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(filename, name);
data/iptux-0.7.6/src/iptux/wrapper.cpp:191:10: [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.
sscanf((char *)buf, "%" SCNx32, &headsize) != 1 || headsize > offset) {
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1545:39: [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.
g_get_home_dir());
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1592:39: [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.
g_get_home_dir());
data/iptux-0.7.6/src/iptux/DialogBase.cpp:428:39: [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.
g_get_home_dir());
data/iptux-0.7.6/src/iptux/ProgramData.cpp:178:43: [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.
path = config.GetString("archive_path", g_get_home_dir());
data/iptux-0.7.6/src/iptux/ShareFile.cpp:415:39: [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.
g_get_home_dir());
data/iptux-0.7.6/src/iptux/callback.cpp:89:39: [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.
g_get_home_dir());
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:64: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).
int AnalogFS::open(const char *fn, int flags) { return open(fn, flags, 0); }
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:64:56: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int AnalogFS::open(const char *fn, int flags) { return open(fn, flags, 0); }
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:73: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).
int AnalogFS::open(const char *fn, int flags, mode_t mode) {
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:74: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 tpath[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:82: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).
if ((fd = ::open(tfn, flags, mode)) == -1)
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:86: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).
if ((fd = ::open(tpath, flags, mode)) == -1)
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:99: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 tpath[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:118: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 tpath[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:168: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 tpath[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:192: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 tpath[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/AnalogFS.h:29: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).
int open(const char *fn, int flags);
data/iptux-0.7.6/src/iptux/AnalogFS.h:30: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).
int open(const char *fn, int flags, mode_t mode);
data/iptux-0.7.6/src/iptux/AnalogFS.h:39: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 path[MAX_PATHLEN]; //当前工作路径
data/iptux-0.7.6/src/iptux/Command.cpp:232: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 packetstr[11]; // 10 +1 =11
data/iptux-0.7.6/src/iptux/Command.cpp:300: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 attrstr[35]; // 8+1+8+1+16 +1 =35
data/iptux-0.7.6/src/iptux/Command.cpp:338: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 attrstr[20]; // 8+1+8+1+1 +1 =20
data/iptux-0.7.6/src/iptux/Command.cpp:465:49: [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).
(xwrite(sock, buf, size) == -1) || ((fd = open(path, O_RDONLY)) == -1))
data/iptux-0.7.6/src/iptux/Command.cpp:524: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, ptr, size);
data/iptux-0.7.6/src/iptux/Command.cpp:618: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/Command.cpp:624: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).
if ((fd = open(path, O_RDONLY)) == -1) return;
data/iptux-0.7.6/src/iptux/Command.h:59: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[MAX_UDPLEN]; //数据缓冲区
data/iptux-0.7.6/src/iptux/CoreThread.cpp:214: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/CoreThread.cpp:944: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 name[9]; // 8 +1 =9
data/iptux-0.7.6/src/iptux/CoreThread.cpp:1146: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[MAX_UDPLEN];
data/iptux-0.7.6/src/iptux/DataSettings.cpp:421: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[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/DataSettings.cpp:506: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/DataSettings.cpp:887: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 path[MAX_PATHLEN], *file;
data/iptux-0.7.6/src/iptux/DataSettings.cpp:946: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 path[MAX_PATHLEN], *file;
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1101:18: [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 (!(stream = fopen(filename, "w"))) {
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1126: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[3][MAX_BUFLEN], *lineptr;
data/iptux-0.7.6/src/iptux/DataSettings.cpp:1132:18: [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 (!(stream = fopen(filename, "r"))) {
data/iptux-0.7.6/src/iptux/DialogBase.cpp:833: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 progresstip[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/DialogGroup.cpp:203: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[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:180: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[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:184: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 ipstr[INET_ADDRSTRLEN];
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:386: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[MAX_BUFLEN], ipstr[INET_ADDRSTRLEN];
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:464: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[MAX_UDPLEN];
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:973: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 progresstip[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:1082: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 progresstip[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/IptuxConfigTest.cpp:15:16: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
string fname(tmpfile);
data/iptux-0.7.6/src/iptux/LogSystem.cpp:35: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/LogSystem.cpp:39: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).
fdc = open(path, O_WRONLY | O_CREAT | O_APPEND, 0644);
data/iptux-0.7.6/src/iptux/LogSystem.cpp:41: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).
fds = open(path, O_WRONLY | O_CREAT | O_APPEND, 0644);
data/iptux-0.7.6/src/iptux/MainWindow.cpp:1275: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 ipstr[INET_ADDRSTRLEN];
data/iptux-0.7.6/src/iptux/MainWindow.cpp:1351: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 ipstr[INET_ADDRSTRLEN];
data/iptux-0.7.6/src/iptux/MainWindow.cpp:1565: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[MAX_BUFLEN], ipstr[INET_ADDRSTRLEN];
data/iptux-0.7.6/src/iptux/MainWindow.cpp:1616: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[MAX_BUFLEN];
data/iptux-0.7.6/src/iptux/MainWindow.cpp:2354: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 ipstr[INET_ADDRSTRLEN], *file;
data/iptux-0.7.6/src/iptux/ProgramData.cpp:210: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 pathbuf[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/RecvFileData.cpp:150: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).
if ((fd = afs.open(file->filepath, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE,
data/iptux-0.7.6/src/iptux/RecvFileData.cpp:270: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 = afs.open(dirname, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE,
data/iptux-0.7.6/src/iptux/RecvFileData.cpp:275:19: [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("/dev/null", O_WRONLY)) == -1) goto end;
data/iptux-0.7.6/src/iptux/RecvFileData.h:41: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[MAX_SOCKLEN]; //数据缓冲区
data/iptux-0.7.6/src/iptux/RevisePal.cpp:216: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/SendFile.cpp:115: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[MAX_UDPLEN];
data/iptux-0.7.6/src/iptux/SendFile.cpp:159: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[MAX_UDPLEN];
data/iptux-0.7.6/src/iptux/SendFileData.cpp:136: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).
if ((fd = open(file->filepath, O_RDONLY | O_LARGEFILE)) == -1) {
data/iptux-0.7.6/src/iptux/SendFileData.cpp:231: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 = afs.open(dirt->d_name, O_RDONLY | O_LARGEFILE)) == -1)
data/iptux-0.7.6/src/iptux/SendFileData.h:42: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[MAX_SOCKLEN]; //数据缓冲区
data/iptux-0.7.6/src/iptux/TcpData.cpp:110: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/TcpData.cpp:139: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).
if ((fd = open(path, O_WRONLY | O_CREAT | O_TRUNC, 0644)) == -1) return;
data/iptux-0.7.6/src/iptux/TcpData.h:39: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[MAX_SOCKLEN]; //缓冲区
data/iptux-0.7.6/src/iptux/UdpData.cpp:61: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(udata.buf, buf, size);
data/iptux-0.7.6/src/iptux/UdpData.cpp:678: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, ptr, size);
data/iptux-0.7.6/src/iptux/UdpData.cpp:708: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/UdpData.cpp:736: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/UdpData.cpp:747: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).
if ((fd = open(path, O_WRONLY | O_CREAT | O_TRUNC, 0644)) == -1) return NULL;
data/iptux-0.7.6/src/iptux/UdpData.h:62: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[MAX_UDPLEN]; //数据缓冲区
data/iptux-0.7.6/src/iptux/dialog.cpp:51: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 ipstr[INET_ADDRSTRLEN], *ptr;
data/iptux-0.7.6/src/iptux/dialog.cpp:97: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 ipstr[INET_ADDRSTRLEN], *text;
data/iptux-0.7.6/src/iptux/support.cpp:147: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 path[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/support.cpp:413: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 ipstr[INET_ADDRSTRLEN], *buf, *ptr;
data/iptux-0.7.6/src/iptux/utils.cpp:191: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[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/utils.cpp:219: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[MAX_BUFLEN], *msg, *ptr;
data/iptux-0.7.6/src/iptux/utils.cpp:437: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 filename[256]; //文件最大长度为255
data/iptux-0.7.6/src/iptux/utils.cpp:449: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((void *)ptr, "xx", 2);
data/iptux-0.7.6/src/iptux/utils.cpp:483: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 filename[512]; //文件最大长度为255
data/iptux-0.7.6/src/iptux/utils.cpp:493:7: [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(filename + len, "::", 2);
data/iptux-0.7.6/src/iptux/utils.cpp:553: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 filename[MAX_PATHLEN];
data/iptux-0.7.6/src/iptux/wrapper.cpp:189:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
((char *)buf)[offset] = '\0';
data/iptux-0.7.6/src/iptux/wrapper.cpp:199:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
((char *)buf)[offset] = '\0';
data/iptux-0.7.6/src/main/iptux.cpp:73: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 buffer[80];
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:30:37: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
if (!::getcwd(path, MAX_PATHLEN)) strcpy(path, "/");
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:54: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).
len = strlen(path);
data/iptux-0.7.6/src/iptux/AnalogFS.cpp:221: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).
len = strlen(tpath);
data/iptux-0.7.6/src/iptux/Command.cpp:523: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).
size = strlen(ptr) + 1;
data/iptux-0.7.6/src/iptux/Command.cpp:539: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).
size = strlen(buf);
data/iptux-0.7.6/src/iptux/Command.cpp:544: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).
size += strlen(ptr);
data/iptux-0.7.6/src/iptux/Command.cpp:549: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).
size += strlen(ptr);
data/iptux-0.7.6/src/iptux/Command.cpp:554: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).
size += strlen(ptr);
data/iptux-0.7.6/src/iptux/Command.cpp:561: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).
size += strlen(ptr);
data/iptux-0.7.6/src/iptux/Command.cpp:565: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).
size += strlen(ptr) + 1;
data/iptux-0.7.6/src/iptux/Command.cpp:584: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).
size += strlen(pptr) + 1;
data/iptux-0.7.6/src/iptux/Command.cpp:602: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).
size += strlen(pptr) + 1;
data/iptux-0.7.6/src/iptux/Command.cpp:606: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).
size += strlen(pptr) + 1;
data/iptux-0.7.6/src/iptux/Command.cpp:610: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).
size += strlen(pptr) + 1;
data/iptux-0.7.6/src/iptux/DialogPeer.cpp:495: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 += strlen(ptr);
data/iptux-0.7.6/src/iptux/LogSystem.cpp:71: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).
write(fdc, log, strlen(log));
data/iptux-0.7.6/src/iptux/LogSystem.cpp:94: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).
write(fds, log, strlen(log));
data/iptux-0.7.6/src/iptux/RecvFileData.cpp:258: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 (strlen(afs.cwd()) < strlen(file->filepath)) {
data/iptux-0.7.6/src/iptux/RecvFileData.cpp:258: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).
if (strlen(afs.cwd()) < strlen(file->filepath)) {
data/iptux-0.7.6/src/iptux/SendFile.cpp:141: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).
len += strlen(ptr);
data/iptux-0.7.6/src/iptux/SendFile.cpp:189: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).
len += strlen(ptr);
data/iptux-0.7.6/src/iptux/SendFileData.cpp:224: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).
headsize = strlen(buf);
data/iptux-0.7.6/src/iptux/SendFileData.cpp:256: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).
headsize = strlen(buf);
data/iptux-0.7.6/src/iptux/ShareFile.cpp:487:47: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
epasswd = g_base64_encode((guchar *)passwd, strlen(passwd));
data/iptux-0.7.6/src/iptux/TcpData.cpp:140: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).
RecvSublayerData(fd, strlen(buf) + 1);
data/iptux-0.7.6/src/iptux/UdpData.cpp:658: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).
ptr = buf + strlen(buf) + 1;
data/iptux-0.7.6/src/iptux/UdpData.cpp:661: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).
ptr += strlen(ptr) + 1;
data/iptux-0.7.6/src/iptux/UdpData.cpp:676: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(ptr);
data/iptux-0.7.6/src/iptux/UdpData.cpp:742: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 ((len = strlen(buf) + 1) >= size) return NULL;
data/iptux-0.7.6/src/iptux/UdpData.cpp:828:49: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
epasswd = g_base64_encode((guchar *)passwd, strlen(passwd));
data/iptux-0.7.6/src/iptux/callback.cpp:59: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 (length == -1) length = strlen(text);
data/iptux-0.7.6/src/iptux/support.cpp:248: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 (strncasecmp(uri, prl, strlen(prl)) == 0)
data/iptux-0.7.6/src/iptux/support.cpp:249:58: [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).
filelist = g_slist_append(filelist, g_strdup(uri + strlen(prl)));
data/iptux-0.7.6/src/iptux/support.cpp:424: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).
ptr += strlen(ptr);
data/iptux-0.7.6/src/iptux/utils.cpp:66:60: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (!(ptr = strpbrk(pptr, ",;\x20\t"))) ptr = pptr + strlen(pptr);
data/iptux-0.7.6/src/iptux/utils.cpp:177: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 ((len = ptr ? (ptr - pptr) : strlen(pptr))) {
data/iptux-0.7.6/src/iptux/utils.cpp:325: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).
ptr += strlen(ptr) + 1;
data/iptux-0.7.6/src/iptux/utils.cpp:420: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).
if ((len = ptr ? ptr - pptr : strlen(pptr)) == 0) return NULL;
data/iptux-0.7.6/src/iptux/utils.cpp:555:3: [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(filename, "/");
data/iptux-0.7.6/src/iptux/wrapper.cpp:63:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((size = read(fd, (char *)buf + offset, count - offset)) == -1) {
data/iptux-0.7.6/src/iptux/wrapper.cpp:90:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((size = read(fd, (char *)buf + offset, count - offset)) == -1) {
data/iptux-0.7.6/src/iptux/wrapper.cpp:128:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((size = read(fd, (char *)buf + offset, count - offset)) == -1) {
data/iptux-0.7.6/src/iptux/wrapper.cpp:161:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((size = read(fd, (char *)buf + offset, count - offset)) == -1) {
data/iptux-0.7.6/src/iptux/wrapper.cpp:193:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((size = read(fd, (char *)buf + offset, count - offset)) == -1) {
ANALYSIS SUMMARY:
Hits = 205
Lines analyzed = 18208 in approximately 0.49 seconds (37376 lines/second)
Physical Source Lines of Code (SLOC) = 12245
Hits@level = [0] 80 [1] 44 [2] 82 [3] 6 [4] 73 [5] 0
Hits@level+ = [0+] 285 [1+] 205 [2+] 161 [3+] 79 [4+] 73 [5+] 0
Hits/KSLOC@level+ = [0+] 23.2748 [1+] 16.7415 [2+] 13.1482 [3+] 6.45161 [4+] 5.96162 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.