- ../../EX_browser_sources.c:84: [4] (buffer) fscanf: The scanf() family's %s operation, without a limit specification, permits buffer overflows. Specify a limit to %s, or use a different input function.
- ../../cl_input.c:625: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../cl_input.c:628: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../cl_screen.c:1592: [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. Use a constant for the format specification.
- ../../cl_screen.c:1669: [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. Use a constant for the format specification.
- ../../cmd.c:1036: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../cmd.c:1440: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../cmd.c:1451: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../cmd.c:2192: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../common.c:585: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../common.c:682: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../common.c:934: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../common.c:967: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../common.c:1018: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../config_manager.c:421: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:422: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:772: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:778: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:784: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:790: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:796: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:800: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../config_manager.c:804: [4] (format) fprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../console.c:541: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../gl_md3.c:402: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../gl_model.c:750: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../gl_model.c:759: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../gl_model.c:777: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../gl_model.c:782: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../host.c:381: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../hud.c:1141: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../hud.c:1145: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../hud_common.c:2158: [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. Use a constant for the format specification.
- ../../hud_common.c:4133: [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. Use a constant for the format specification.
- ../../keys.c:1351: [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. Use a constant for the format specification.
- ../../keys.c:1408: [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. Use a constant for the format specification.
- ../../keys.c:1414: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../match_tools.c:201: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../match_tools.c:203: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../match_tools.c:811: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:961: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1041: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1046: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1047: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1079: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1231: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1302: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1307: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../match_tools.c:1308: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../mp3_audacious.c:168: [4] (shell) execvp: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../mp3_mpd.c:152: [4] (shell) execvp: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../mp3_xmms.c:141: [4] (shell) execvp: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../mp3_xmms2.c:179: [4] (shell) execvp: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../net_chan.c:137: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../parser.c:17: [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. Use a constant for the format specification.
- ../../pr_exec.c:214: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../q_shared.c:185: [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. Use a constant for the format specification.
- ../../q_shared.c:196: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../qtv.c:227: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../r_model.c:935: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../skin.c:98: [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. Use a constant for the format specification.
- ../../stats_grid.c:178: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../stats_grid.c:182: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../sv_save.c:157: [4] (buffer) fscanf: The scanf() family's %s operation, without a limit specification, permits buffer overflows. Specify a limit to %s, or use a different input function.
- ../../sv_save.c:171: [4] (buffer) fscanf: The scanf() family's %s operation, without a limit specification, permits buffer overflows. Specify a limit to %s, or use a different input function.
- ../../sv_save.c:189: [4] (buffer) fscanf: The scanf() family's %s operation, without a limit specification, permits buffer overflows. Specify a limit to %s, or use a different input function.
- ../../sv_send.c:97: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sv_send.c:111: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sv_send.c:134: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sv_sys_unix.c:98: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sv_sys_unix.c:118: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sv_sys_win.c:54: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sv_sys_win.c:158: [4] (format) vprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../sv_user.c:687: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sys_linux.c:86: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sys_linux.c:131: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sys_linux.c:603: [4] (misc) getlogin: It's often easy to fool getlogin. Sometimes it does not work at all, because some program messed up the utmp file. Often, it gives only the first 8 characters of the login name. The user currently logged in on the controlling tty of our program need not be the user who started it. Avoid getlogin() for security-related purposes. Use getpwuid(geteuid()) and extract the desired information instead.
- ../../sys_mac.c:292: [4] (format) vsprintf: Potential format string problem. Make format string constant.
- ../../sys_mac.c:312: [4] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf.
- ../../sys_mac.c:332: [4] (format) vsprintf: Potential format string problem. Make format string constant.
- ../../sys_mac.c:365: [4] (format) vprintf: If format strings can be influenced by an attacker, they can be exploited. Use a constant for the format specification.
- ../../sys_mac.c:382: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../sys_mac.c:384: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../sys_mac.c:404: [4] (format) vsprintf: Potential format string problem. Make format string constant.
- ../../sys_mac.c:1252: [4] (buffer) strcat: Does not check for buffer overflows when concatenating to destination. Consider using strncat or strlcat (warning, strncat is easily misused).
- ../../sys_win.c:326: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sys_win.c:354: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../sys_win.c:719: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../teamplay.c:1991: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../teamplay.c:2107: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../teamplay.c:2223: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2225: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2227: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2231: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2233: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2235: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2244: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2254: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../teamplay.c:2254: [4] (shell) system: This causes a new program to execute and is difficult to use safely. try using a library call that implements the same functionality if available.
- ../../tp_msgs.c:108: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate. Use a constant for the format specification.
- ../../tp_triggers.c:183: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../utils.c:473: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../utils.c:747: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../vid_mac.c:473: [4] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf.
- ../../vid_wgl.c:1451: [4] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf.
- ../../vid_wgl.c:1459: [4] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf.
- ../../vx_stuff.c:331: [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. Use a constant for the format specification.
- ../../xsd.c:166: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused).
- ../../cl_demo.c:2153: [3] (shell) CreateProcess: This causes a new process to execute and is difficult to use safely. Specify the application path in the first argument, NOT as part of the second, or embedded spaces could allow an attacker to force a different program to run.
- ../../cl_demo.c:2153: [3] (shell) CreateProcess: This causes a new process to execute and is difficult to use safely. Specify the application path in the first argument, NOT as part of the second, or embedded spaces could allow an attacker to force a different program to run.
- ../../cl_demo.c:2220: [3] (shell) CreateProcess: This causes a new process to execute and is difficult to use safely. Specify the application path in the first argument, NOT as part of the second, or embedded spaces could allow an attacker to force a different program to run.
- ../../cl_demo.c:2220: [3] (shell) CreateProcess: This causes a new process to execute and is difficult to use safely. Specify the application path in the first argument, NOT as part of the second, or embedded spaces could allow an attacker to force a different program to run.
- ../../cl_ents.c:237: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../cl_ents.c:241: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../cl_ents.c:248: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../cl_ents.c:258: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../cl_ents.c:266: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../common.c:326: [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. Check environment variables carefully before using them.
- ../../common.c:369: [3] (tmpfile) GetTempFileName: Temporary file race condition in certain cases (e.g., if run as SYSTEM in many versions of Windows).
- ../../common.c:381: [3] (tmpfile) tempnam: Temporary file race condition.
- ../../fs.c:929: [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. Check environment variables carefully before using them.
- ../../fs.c:1146: [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. Check environment variables carefully before using them.
- ../../image.c:611: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../image.c:1933: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../in_win.c:619: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../in_win.c:872: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../in_win.c:1133: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../modules.c:81: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../movie_avi.c:85: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../movie_avi.c:126: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../mp3_mpd.c:98: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../mp3_mpd.c:120: [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. Check environment variables carefully before using them.
- ../../mp3_mpd.c:121: [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. Check environment variables carefully before using them.
- ../../mp3_mpd.c:347: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../mp3_winamp.c:207: [3] (shell) CreateProcess: This causes a new process to execute and is difficult to use safely. Specify the application path in the first argument, NOT as part of the second, or embedded spaces could allow an attacker to force a different program to run.
- ../../mp3_winamp.c:207: [3] (shell) CreateProcess: This causes a new process to execute and is difficult to use safely. Specify the application path in the first argument, NOT as part of the second, or embedded spaces could allow an attacker to force a different program to run.
- ../../mp3_xmms2.c:127: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../mp3_xmms2.c:156: [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. Check environment variables carefully before using them.
- ../../net_chan.c:86: [3] (random) srand: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../snd_ov.c:72: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used. Use registry entry or GetWindowsDirectory to find library path, if you aren't already.
- ../../sys_linux.c:483: [3] (buffer) realpath: This function does not protect against buffer overflows, and some implementations can overflow internally. 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.
- ../../sys_linux.c:491: [3] (buffer) realpath: This function does not protect against buffer overflows, and some implementations can overflow internally. 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.
- ../../sys_mac.c:1479: [3] (buffer) realpath: This function does not protect against buffer overflows, and some implementations can overflow internally. 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.
- ../../sys_mac.c:1487: [3] (buffer) realpath: This function does not protect against buffer overflows, and some implementations can overflow internally. 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.
- ../../vid_x11.c:365: [3] (random) random: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../vid_x11.c:407: [3] (random) srandom: This function is not sufficiently random for security-related functions such as key and nonce creation. use a more secure technique for acquiring random values.
- ../../Ctrl.c:116: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../Ctrl.c:140: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../Ctrl_EditBox.c:14: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../Ctrl_EditBox.c:85: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../Ctrl_PageViewer.c:134: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../Ctrl_PageViewer.c:188: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../Ctrl_Tab.c:74: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../Ctrl_Tab.c:81: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../Ctrl_Tab.c:130: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:106: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:236: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:237: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:426: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:457: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:582: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_FileList.c:749: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:843: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_FileList.c:896: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:964: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1093: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1244: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1271: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1272: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1476: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_FileList.c:1490: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1491: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1603: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_FileList.c:1643: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1644: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1647: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_FileList.c:1775: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_FileList.c:1810: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser.c:44: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:180: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:194: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:243: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser.c:280: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:445: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:464: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:538: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:563: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:623: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:635: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:660: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:720: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:935: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:969: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser.c:971: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser.c:973: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser.c:1093: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1147: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1173: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1219: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1290: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1319: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1401: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1545: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1678: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1780: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:1908: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2026: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2070: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2089: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2229: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2241: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2259: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2364: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2376: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser.c:2583: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../EX_browser_net.c:31: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_net.c:38: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../EX_browser_net.c:128: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_net.c:249: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../EX_browser_net.c:262: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_net.c:425: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_net.c:468: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_ping.c:155: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_ping.c:700: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:68: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:80: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:123: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:150: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser_sources.c:168: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:182: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:221: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:285: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:381: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:495: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:533: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:547: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../EX_browser_sources.c:591: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../EX_browser_sources.c:649: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../auth.c:45: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../auth.c:57: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../auth.c:87: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../auth.c:88: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../auth.c:89: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../auth.c:114: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../auth.c:133: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cd_linux.c:55: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cd_linux.c:463: [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?.
- ../../cl_cam.c:168: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cam.c:181: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_cam.c:628: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cam.c:879: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cam.c:1020: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_cmd.c:94: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:142: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:296: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:362: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:403: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:458: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:528: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:555: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:573: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:634: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:693: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_cmd.c:753: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:938: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_cmd.c:950: [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?.
- ../../cl_cmd.c:952: [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?.
- ../../cl_cmd.c:979: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:66: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:161: [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?.
- ../../cl_demo.c:412: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:436: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:548: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:818: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:834: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_demo.c:854: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_demo.c:1006: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_demo.c:1093: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_demo.c:1360: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1361: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1418: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1503: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1514: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1615: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1616: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1752: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1884: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:1914: [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?.
- ../../cl_demo.c:1983: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2061: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2065: [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?.
- ../../cl_demo.c:2085: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2137: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused). Risk is low because the source is a constant string.
- ../../cl_demo.c:2181: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2182: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2255: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2256: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2265: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2313: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2344: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2345: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2361: [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?.
- ../../cl_demo.c:2762: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2767: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2969: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:2972: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3001: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3002: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3003: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3141: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_demo.c:3195: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3393: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3417: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_demo.c:3422: [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?.
- ../../cl_demo.c:3686: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_demo.c:3691: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_ents.c:60: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_ents.c:1516: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_ents.c:1676: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_input.c:93: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_input.c:120: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_input.c:619: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:258: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:270: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:279: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:323: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:331: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:364: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:426: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:436: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:446: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:455: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:464: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:478: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:485: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:579: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:580: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:604: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:616: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:770: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:959: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:1208: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:1234: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_main.c:1520: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:2226: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:2434: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:2537: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_main.c:2597: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_main.c:2698: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_main.c:2699: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_nqdemo.c:376: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:860: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:905: [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?.
- ../../cl_parse.c:1105: [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?.
- ../../cl_parse.c:1168: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_parse.c:1217: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_parse.c:1283: [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?.
- ../../cl_parse.c:1334: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:1410: [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?.
- ../../cl_parse.c:1421: [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?.
- ../../cl_parse.c:1428: [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?.
- ../../cl_parse.c:1439: [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?.
- ../../cl_parse.c:1584: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:1650: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_parse.c:1899: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:1900: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:1970: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:1997: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2002: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2020: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2038: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2039: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2042: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2043: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2113: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:2121: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2131: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_parse.c:2145: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:2318: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:2392: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:2538: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_parse.c:2574: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_screen.c:81: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:236: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:254: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:593: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:619: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:681: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:705: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:733: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:757: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:1048: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:1467: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:1524: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:1750: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:1850: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1862: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1863: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1864: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1865: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1866: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1867: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1926: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1932: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1944: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1945: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1946: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1947: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1948: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:1949: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2259: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2260: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2261: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2266: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2291: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2292: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2319: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2324: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2415: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_screen.c:2662: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:2878: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:3407: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:3555: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:3593: [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?.
- ../../cl_screen.c:3611: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:3666: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:3769: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:3770: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4327: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4862: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4863: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4864: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4865: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4866: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:4868: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_screen.c:5254: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_screen.c:5286: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_slist.c:41: [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?.
- ../../cl_slist.c:92: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_slist.c:93: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_slist.c:94: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_slist.c:108: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_slist.c:111: [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?.
- ../../cl_tcl.c:149: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_tcl.c:211: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_tcl.c:322: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_tcl.c:569: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_tcl.c:577: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cl_tcl.c:585: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cl_view.c:443: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_view.c:444: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_view.c:445: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cl_view.c:446: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cmd.c:143: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmd.c:157: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmd.c:158: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmd.c:172: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmd.c:187: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmd.c:197: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:398: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:452: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:453: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:637: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:657: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmd.c:921: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:1378: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:1551: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:1554: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:1759: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:1847: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:2051: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:2062: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cmd.c:2105: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cmd.c:2130: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:2140: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cmd.c:2171: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmd.c:2179: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cmodel.c:47: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmodel.c:49: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cmodel.c:553: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmodel.c:882: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmodel.c:905: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../cmodel.c:1032: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../com_msg.c:412: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../com_msg.c:437: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../com_msg.c:478: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../common.c:60: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:81: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:215: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:245: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused). Risk is low because the source is a constant string.
- ../../common.c:251: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../common.c:349: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:351: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:398: [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?.
- ../../common.c:412: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:577: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:616: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:617: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:653: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:693: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:729: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:806: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:894: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../common.c:931: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:960: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common.c:981: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common_draw.c:35: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common_draw.c:359: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common_draw.c:435: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../common_draw.c:582: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common_draw.c:726: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common_draw.c:740: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../common_draw.c:755: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:65: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:259: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:264: [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?.
- ../../config_manager.c:655: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:666: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:677: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../config_manager.c:759: [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?.
- ../../config_manager.c:761: [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?.
- ../../config_manager.c:827: [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?.
- ../../config_manager.c:829: [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?.
- ../../config_manager.c:864: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:881: [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?.
- ../../config_manager.c:887: [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?.
- ../../config_manager.c:926: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:933: [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?.
- ../../config_manager.c:952: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../config_manager.c:974: [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?.
- ../../config_manager.c:982: [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?.
- ../../config_manager.c:1018: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../console.c:107: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../console.c:121: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../console.c:209: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../console.c:363: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../console.c:368: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../console.c:391: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../console.c:422: [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?.
- ../../console.c:537: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../console.c:977: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cpu.c:38: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cvar.c:127: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cvar.c:333: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cvar.c:457: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cvar.c:854: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cvar.c:1057: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../cvar.c:1083: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cvar.c:1084: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../cvar.c:1119: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../document_rendering.c:40: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../document_rendering.c:127: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../document_rendering.c:508: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../document_rendering.c:587: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../document_rendering.c:602: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../document_rendering.c:683: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../ez_label.c:395: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../ez_label.c:520: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../ez_label.c:594: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../ez_label.c:1123: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fmod.c:153: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fmod.c:169: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fmod.c:388: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fragstats.c:735: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:54: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:58: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:59: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:60: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:61: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:64: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:65: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:73: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:83: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:89: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:188: [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?.
- ../../fs.c:253: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:282: [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?.
- ../../fs.c:299: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:303: [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?.
- ../../fs.c:305: [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?.
- ../../fs.c:317: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:358: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:362: [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?.
- ../../fs.c:364: [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?.
- ../../fs.c:385: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:391: [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?.
- ../../fs.c:437: [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?.
- ../../fs.c:484: [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?.
- ../../fs.c:498: [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?.
- ../../fs.c:528: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:674: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:721: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:817: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:818: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:822: [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?.
- ../../fs.c:884: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:914: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1253: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1391: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1512: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1530: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1689: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1749: [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?.
- ../../fs.c:1778: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1814: [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?.
- ../../fs.c:1824: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1888: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1889: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:1989: [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?.
- ../../fs.c:2113: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:2335: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:2407: [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?.
- ../../fs.c:2466: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:2622: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3049: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3050: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3112: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3113: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3152: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3185: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3242: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3274: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../fs.c:3290: [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?.
- ../../fs.c:3418: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../fs.c:3567: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../fs.c:3568: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../fs.c:3593: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:277: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:466: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:467: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:468: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:503: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:539: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:621: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:647: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:655: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:986: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:1024: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:1832: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_draw.c:1859: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_draw.c:1892: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_md3.c:242: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_md3.c:275: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_md3.c:276: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_md3.c:277: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_md3.c:306: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_md3.c:475: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_mesh.c:306: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:44: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:221: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:404: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:405: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:560: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:577: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:586: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:597: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:802: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:845: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:858: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:865: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:1357: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:1516: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:1542: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:1568: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:1780: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:1789: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:1810: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_model.c:1978: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:1994: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_model.c:2011: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_ngraph.c:82: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_ngraph.c:142: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_ngraph.c:204: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_rmain.c:1826: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_rmisc.c:86: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_rsurf.c:989: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_rsurf.c:990: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_rsurf.c:1318: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_texture.c:64: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_texture.c:304: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_texture.c:501: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_texture.c:524: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_texture.c:590: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_texture.c:610: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_texture.c:617: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_texture.c:834: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../gl_texture.c:891: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_texture.c:928: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../gl_warp.c:542: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:80: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:95: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:180: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:181: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:186: [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?.
- ../../host.c:196: [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?.
- ../../host.c:208: [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?.
- ../../host.c:216: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../host.c:280: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:373: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:460: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:587: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:593: [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?.
- ../../host.c:611: [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?.
- ../../host.c:668: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../host.c:762: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud.c:135: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud.c:539: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud.c:659: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../hud.c:819: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud.c:831: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../hud.c:1078: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud.c:1103: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../hud.c:1173: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud.c:1331: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:231: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:264: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:304: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:351: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:356: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:481: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:1707: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:1947: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:2143: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:2682: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:3095: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:3096: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:3201: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:3898: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:3926: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:4005: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:4006: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:4289: [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?.
- ../../hud_common.c:4655: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:4699: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:4879: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:5126: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../hud_common.c:5134: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../hud_common.c:5858: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../ignore.c:39: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../ignore.c:42: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../ignore.c:293: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../ignore.c:341: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:150: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:196: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:201: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:276: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:322: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:328: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:840: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:859: [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?.
- ../../image.c:861: [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?.
- ../../image.c:937: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:953: [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?.
- ../../image.c:955: [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?.
- ../../image.c:1361: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:1462: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:1478: [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?.
- ../../image.c:1480: [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?.
- ../../image.c:1556: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:1569: [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?.
- ../../image.c:1571: [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?.
- ../../image.c:1883: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:2036: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:2046: [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?.
- ../../image.c:2048: [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?.
- ../../image.c:2189: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../image.c:2201: [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?.
- ../../image.c:2203: [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?.
- ../../image.c:2316: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../image.c:2557: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../in_win.c:869: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:296: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:301: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:397: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:424: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:432: [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?.
- ../../keymap.c:602: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:671: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:748: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap.c:928: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keymap_x11.c:204: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:85: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:308: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:342: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:367: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:400: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../keys.c:563: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:598: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../keys.c:659: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1106: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../keys.c:1293: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../keys.c:1324: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1374: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1375: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1424: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1568: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1594: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../keys.c:1632: [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?.
- ../../keys.c:1659: [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?.
- ../../keys.c:1883: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../linux_glimp.c:373: [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?.
- ../../linux_glimp.c:547: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../linux_glimp.c:550: [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?.
- ../../linux_glimp.c:1483: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../linux_glimp.c:1505: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../logging.c:36: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../logging.c:45: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../logging.c:118: [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?.
- ../../logging.c:120: [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?.
- ../../logging.c:162: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../logging.c:208: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../logging.c:235: [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?.
- ../../logging.c:237: [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?.
- ../../logging.c:257: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../logging.c:277: [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?.
- ../../match_tools.c:74: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:106: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:126: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:160: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:178: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:233: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:283: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:284: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:285: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:286: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:287: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:291: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:292: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:293: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:294: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:301: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:302: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:304: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:305: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:306: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:307: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:358: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:483: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:583: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:615: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:727: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:808: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:809: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:1021: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:1076: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:1077: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../match_tools.c:1294: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../md4.c:56: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../md4.c:97: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../md4.c:149: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../md4.c:161: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../md4.c:166: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../md4.c:168: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../md4.c:191: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu.c:261: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu.c:264: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu.c:973: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu.c:979: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu.c:992: [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?.
- ../../menu.c:1002: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../menu_demo.c:73: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:74: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:75: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:114: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:115: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:136: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:288: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:289: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:290: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:305: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:306: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:307: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:510: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../menu_demo.c:538: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_demo.c:894: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_mp3player.c:28: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_mp3player.c:32: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_mp3player.c:95: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_mp3player.c:289: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_mp3player.c:410: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_multiplayer.c:159: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../menu_multiplayer.c:170: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../modules.c:37: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../modules.c:75: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../movie.c:64: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../movie.c:69: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../movie.c:186: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../movie.c:199: [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?.
- ../../movie.c:201: [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?.
- ../../movie.c:266: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../movie.c:336: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../mp3_audacious.c:158: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_audacious.c:297: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_mpd.c:129: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../mp3_mpd.c:142: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_mpd.c:303: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_mpd.c:414: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_player.c:102: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_player.c:133: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_player.c:186: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_winamp.c:127: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_winamp.c:185: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_winamp.c:338: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_winamp.c:403: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_xmms.c:131: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_xmms.c:270: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_xmms2.c:169: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_xmms2.c:532: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mp3_xmms2.c:637: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_autotrack.c:365: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:117: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:118: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:119: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:120: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:156: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:210: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:258: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../mvd_utils.c:270: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:379: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:380: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:804: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_utils.c:997: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_xmlstats.c:29: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../mvd_xmlstats.c:261: [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?.
- ../../net.c:92: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../net.c:103: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../net.c:119: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../net.c:139: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../net.c:202: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../net.c:222: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../net.c:348: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../net.c:435: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../net.c:765: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../net.c:834: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../net.c:882: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../net.c:894: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../net_chan.c:134: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../net_chan.c:212: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../parser.c:656: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../parser.c:739: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../pr_cmds.c:36: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_cmds.c:47: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_cmds.c:1340: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_cmds.c:1400: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../pr_cmds.c:1617: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:189: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:233: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:277: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:300: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:491: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:552: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:582: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../pr_edict.c:613: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_edict.c:860: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_exec.c:211: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../pr_exec.c:578: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../q_shared.c:159: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../q_shared.c:398: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../q_shared.c:481: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:490: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:504: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:516: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:548: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:825: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:834: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../q_shared.c:836: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../qtv.c:52: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../qtv.c:137: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../qtv.c:184: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../qtv.c:220: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../qtv.c:413: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../qtv.c:414: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../r_draw.c:149: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_draw.c:150: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_draw.c:151: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_draw.c:257: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_draw.c:1159: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_draw.c:1168: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_draw.c:1180: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_draw.c:1201: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_draw.c:1243: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_draw.c:1411: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_misc.c:37: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_misc.c:60: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_misc.c:67: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_misc.c:73: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_misc.c:210: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_misc.c:283: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_misc.c:372: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_model.c:36: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_model.c:282: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:294: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:309: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:341: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:348: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:459: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:469: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:909: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_model.c:1024: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:1258: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_model.c:1291: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_part.c:265: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_part.c:271: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../r_sprite.c:73: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../r_sprite.c:81: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sbar.c:353: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:401: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:463: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:650: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:751: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:952: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:953: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:989: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1033: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1095: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1096: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1200: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1411: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1540: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1678: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sbar.c:1758: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:99: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:109: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:136: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:211: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:230: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:479: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:540: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:556: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../settings_page.c:633: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:26: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:30: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:35: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:37: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sha1.c:103: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sha1.c:111: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sha1.c:117: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:120: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:149: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:159: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sha1.c:177: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../skin.c:45: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../skin.c:79: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../skin.c:109: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../skin.c:169: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../skin.c:305: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../skin.c:356: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../snd_dma.c:805: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_dma.c:823: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_mac.c:36: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_mac.c:40: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_mac.c:163: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../snd_mem.c:221: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_oss.c:52: [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?.
- ../../snd_ov.c:117: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_ov.c:118: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_ov.c:131: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../snd_ov.c:224: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../stats_grid.c:318: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_ccmds.c:49: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_ccmds.c:62: [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?.
- ../../sv_ccmds.c:65: [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?.
- ../../sv_ccmds.c:85: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_ccmds.c:102: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_ccmds.c:150: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_ccmds.c:164: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_ccmds.c:298: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_ccmds.c:468: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_ccmds.c:469: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_ccmds.c:470: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_ccmds.c:521: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_ccmds.c:543: [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?.
- ../../sv_ccmds.c:553: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_ccmds.c:569: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_init.c:29: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_init.c:31: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:216: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:293: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:294: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:332: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:335: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:368: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:403: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_main.c:407: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_main.c:417: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:427: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:434: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:435: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:579: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:722: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:724: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:742: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:806: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:814: [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?.
- ../../sv_main.c:829: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:969: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:1004: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:1198: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_main.c:1284: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_main.c:1289: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_master.c:31: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_master.c:62: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_master.c:92: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_save.c:36: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_save.c:40: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_save.c:42: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_save.c:53: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_save.c:94: [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?.
- ../../sv_save.c:96: [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?.
- ../../sv_save.c:129: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_save.c:145: [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?.
- ../../sv_send.c:39: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_send.c:91: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_send.c:106: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_send.c:129: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_send.c:571: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_sys_unix.c:95: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_sys_unix.c:114: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_sys_unix.c:155: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_sys_win.c:51: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_sys_win.c:93: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:105: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:192: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:199: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:236: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:243: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:280: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:287: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:293: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:345: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:352: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:456: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:504: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:505: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:567: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:650: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:650: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:650: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:679: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:711: [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?.
- ../../sv_user.c:753: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:774: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sv_user.c:893: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:1038: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:1083: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:1103: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sv_user.c:1117: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:1341: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../sv_user.c:1490: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:77: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:123: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:210: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:265: [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?.
- ../../sys_linux.c:289: [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?.
- ../../sys_linux.c:482: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:499: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:500: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:501: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:578: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:598: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:622: [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?.
- ../../sys_linux.c:642: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_linux.c:658: [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?.
- ../../sys_mac.c:132: [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?.
- ../../sys_mac.c:147: [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?.
- ../../sys_mac.c:195: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:196: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:197: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:289: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:329: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:400: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:407: [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?.
- ../../sys_mac.c:413: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:505: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../sys_mac.c:686: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:770: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:817: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../sys_mac.c:1141: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:1478: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_mac.c:1511: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:209: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:210: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:211: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:320: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:345: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:440: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:599: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:733: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:734: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../sys_win.c:980: [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?.
- ../../sys_win.c:1181: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:149: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:154: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:237: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:328: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:868: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1121: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../teamplay.c:1139: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1159: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1322: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1406: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1407: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1630: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../teamplay.c:1632: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../teamplay.c:1633: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../teamplay.c:1698: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../teamplay.c:1718: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1850: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1851: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:1886: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:2072: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:2116: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused). Risk is low because the source is a constant string.
- ../../teamplay.c:2138: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:2146: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:2242: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:2416: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:3063: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../teamplay.c:3238: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../textencoding.c:30: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../textencoding.c:58: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../textencoding.c:161: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../textencoding.c:162: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../textencoding.c:300: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../tp_msgs.c:90: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tp_msgs.c:102: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tp_triggers.c:57: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tp_triggers.c:142: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tp_triggers.c:221: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tp_triggers.c:222: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tp_triggers.c:574: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../tr_init.c:142: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../tr_init.c:191: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:34: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:45: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:57: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:100: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:164: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:177: [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?.
- ../../utils.c:251: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:458: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:488: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:557: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:558: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../utils.c:589: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../utils.c:797: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../version.c:33: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../version.c:35: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../version.c:55: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../version.c:56: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../version.c:86: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_doomwad.c:34: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_doomwad.c:39: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_doomwad.c:54: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_doomwad.c:55: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_doomwad.c:56: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_gzip.c:40: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_mmap.c:57: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vfs_mmap.c:83: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vfs_os.c:92: [2] (tmpfile) tmpfile: Function tmpfile() has a security flaw on some systems (e.g., older System V systems).
- ../../vfs_os.c:124: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_os.c:137: [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?.
- ../../vfs_os.c:167: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_os.c:182: [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?.
- ../../vfs_os.c:208: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_os.c:230: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_os.c:254: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_os.c:272: [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?.
- ../../vfs_os.c:293: [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?.
- ../../vfs_pak.c:30: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_pak.c:44: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_pak.c:50: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_tar.c:38: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_tar.c:96: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_tcp.c:37: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_tcp.c:40: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_tcp.c:106: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vfs_tcp.c:120: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vfs_zip.c:117: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_zip.c:153: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vfs_zip.c:228: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_common_gl.c:234: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_common_gl.c:266: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_glx.c:82: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_glx.c:724: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../vid_glx.c:727: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../vid_glx.c:908: [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?.
- ../../vid_glx.c:916: [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?.
- ../../vid_glx.c:920: [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?.
- ../../vid_mac.c:39: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_mac.c:909: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_mac.c:1333: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../vid_mac.c:1340: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../vid_svgalib.c:138: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:139: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:185: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:250: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:376: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:543: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:566: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:568: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:570: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_svgalib.c:630: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../vid_wgl.c:51: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_wgl.c:89: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_wgl.c:1422: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_wgl.c:1431: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1442: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_wgl.c:1453: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1461: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused). Risk is low because the source is a constant string.
- ../../vid_wgl.c:1549: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1586: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1588: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1595: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1638: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1640: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_wgl.c:1784: [2] (buffer) sprintf: Does not check for buffer overflows. Use snprintf or vsnprintf. Risk is low because the source has a constant maximum length.
- ../../vid_win.c:125: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_win.c:145: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_win.c:900: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_win.c:920: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_win.c:1530: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:1990: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:1991: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:2015: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:2017: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:2054: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:2078: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_win.c:2504: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_x11.c:584: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_x11.c:611: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../vid_x11.c:638: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_x11.c:889: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vid_x11.c:921: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_stuff.c:107: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_stuff.c:282: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_stuff.c:325: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:47: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:56: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:256: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:268: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:280: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:297: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:309: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:323: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:335: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:348: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:355: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:362: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:402: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:418: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:448: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:465: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../vx_tracker.c:587: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../wad.c:127: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../wad.c:246: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../win_glimp.c:1219: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../win_glimp.c:1458: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../xsd.c:54: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../xsd.c:62: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../xsd.c:182: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../xsd.c:183: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../xsd_command.c:139: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../xsd_document.c:1104: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../xsd_variable.c:188: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../zone.c:35: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../zone.c:66: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../zone.c:106: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../zone.c:251: [2] (buffer) char: Statically-sized arrays can be overflowed. Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length.
- ../../zone.c:267: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../zone.c:269: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../zone2.c:419: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../zone2.c:546: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range. 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).
- ../../zone2.c:598: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination. Make sure destination can always hold the source data.
- ../../Ctrl.c:80: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl.c:86: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:31: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:32: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:36: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../Ctrl_EditBox.c:58: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:61: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:64: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:70: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:79: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:79: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:84: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:93: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:97: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_EditBox.c:101: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_PageViewer.c:134: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_PageViewer.c:248: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_PageViewer.c:255: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_PageViewer.c:263: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../Ctrl_PageViewer.c:276: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_PageViewer.c:280: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_PageViewer.c:281: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../Ctrl_Tab.c:101: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:111: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:136: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:254: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:257: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:270: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:278: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:281: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:288: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:297: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:307: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:320: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:322: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:459: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:485: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:489: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:579: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:667: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:914: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1008: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1016: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1204: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1255: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1274: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1476: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1658: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1659: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1675: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1677: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1681: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1683: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1709: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1714: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1726: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1810: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_FileList.c:1838: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_FileList.c:1872: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:185: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:196: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:229: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:297: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:297: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:446: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:465: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:542: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:571: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:572: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:572: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:576: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:587: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:589: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:625: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:628: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:640: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:642: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:646: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:648: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:652: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:654: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:661: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:669: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:1101: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1105: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1112: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1153: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1177: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1231: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1341: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1344: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1346: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1353: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1385: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1388: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1431: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1451: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:1547: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:1547: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:1643: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:1715: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:1909: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser.c:2083: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:2130: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:2150: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:2156: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser.c:2293: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_net.c:75: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:109: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_net.c:156: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_net.c:214: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:220: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:220: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_net.c:224: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:224: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_net.c:229: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:235: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:242: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:245: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_net.c:252: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_net.c:469: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_ping.c:662: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_ping.c:749: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../EX_browser_sources.c:130: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_sources.c:169: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_sources.c:222: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_sources.c:382: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_sources.c:652: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../EX_browser_sources.c:656: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../auth.c:95: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../auth.c:97: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../auth.c:110: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../auth.c:110: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../auth.c:111: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../auth.c:114: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../auth.c:117: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../auth.c:117: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cam.c:178: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cam.c:638: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cam.c:641: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cam.c:880: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:143: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:147: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:149: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:164: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:233: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:353: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:355: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:363: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:374: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:574: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:619: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:628: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_cmd.c:670: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_cmd.c:794: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:420: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:558: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:1430: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:1581: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:1677: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:1910: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:1969: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:1971: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:2067: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:2136: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:2271: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:2283: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:2360: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:2804: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3199: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3202: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3208: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3212: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3213: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3214: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3215: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3218: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3227: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3231: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3232: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3233: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3234: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3237: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3246: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_demo.c:3249: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3288: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3292: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3296: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3298: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3300: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3311: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3316: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3456: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3537: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3544: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3546: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3548: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3553: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3555: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3557: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3568: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_demo.c:3573: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:332: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:350: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:365: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:376: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:401: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:448: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:457: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:479: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:486: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:599: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:605: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:610: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:655: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:656: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:1300: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:1301: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_main.c:1652: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:2041: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../cl_main.c:2241: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:2704: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:2706: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_main.c:2710: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_nqdemo.c:1107: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:462: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:1259: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:1261: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:1396: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:1408: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:1420: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:1427: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:1438: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:1894: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2017: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2324: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2328: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2336: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:2338: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2342: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2345: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:2347: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2351: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2354: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:2356: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2360: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2418: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:2447: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:2540: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_parse.c:2620: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_parse.c:3122: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:602: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:606: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:653: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:779: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:1056: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:1194: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:1563: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:1682: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:1717: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:1729: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:1777: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:1780: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:2688: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:3592: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:3687: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:3799: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:4319: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:4567: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:4598: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:4609: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:4684: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5015: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5016: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5024: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5025: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5033: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5034: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5043: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5044: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5055: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5056: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5066: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5067: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_screen.c:5080: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5086: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5092: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5098: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5110: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5114: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5124: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5128: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5134: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5138: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5147: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5151: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5157: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5168: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5178: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5182: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5188: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5192: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5198: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5202: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5211: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5215: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5221: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5225: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5227: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5233: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5237: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5243: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5247: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5302: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_screen.c:5306: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_slist.c:115: [1] (buffer) getc: Check buffer boundaries if used in a loop.
- ../../cl_slist.c:117: [1] (buffer) getc: Check buffer boundaries if used in a loop.
- ../../cl_slist.c:151: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:78: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:145: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:214: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cl_tcl.c:312: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:425: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:448: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:462: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:476: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cl_tcl.c:530: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:140: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:169: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:358: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:457: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cmd.c:655: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cmd.c:657: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:693: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:806: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:991: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:993: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1029: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1157: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1186: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1202: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1293: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cmd.c:1318: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1323: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1416: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1418: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1427: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1437: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1441: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1448: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1452: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1785: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1890: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1915: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1917: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1928: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1930: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:1934: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:2037: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cmd.c:2043: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../com_msg.c:102: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../com_msg.c:108: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:148: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:163: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:190: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:204: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:236: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:263: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:281: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:281: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:294: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:297: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:297: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:303: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:303: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:329: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:387: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:745: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:745: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:754: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:754: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:754: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:760: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:763: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common.c:765: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:765: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:771: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common.c:1071: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common.c:1075: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:18: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:23: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:57: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:63: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:64: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:77: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:375: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:386: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:388: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:396: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:399: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:416: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:419: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:422: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:425: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:431: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:435: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:669: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:673: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:677: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:681: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:688: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:692: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:697: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:703: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:711: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:715: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:719: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../common_draw.c:768: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:1120: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../common_draw.c:1191: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:103: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:134: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:193: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:220: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:232: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:250: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:262: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:295: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:338: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:340: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:355: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:375: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:387: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:674: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:676: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:769: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:841: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:848: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:852: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:871: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:883: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../config_manager.c:885: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:930: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:963: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:970: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:972: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:978: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../config_manager.c:980: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../console.c:210: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../console.c:1049: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../console.c:1051: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../console.c:1059: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../console.c:1082: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../console.c:1084: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../console.c:1086: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cpu.c:60: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cpu.c:61: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:130: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cvar.c:131: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:163: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:184: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:336: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../cvar.c:338: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:552: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:1069: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:1096: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:1117: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:1118: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:1147: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../cvar.c:1152: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:194: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:195: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:403: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:587: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:683: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:709: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:709: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:724: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:724: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:729: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:778: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../document_rendering.c:784: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:365: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../ez_label.c:376: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:418: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:428: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:571: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../ez_label.c:599: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../ez_label.c:633: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:656: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:832: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../ez_label.c:1142: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fmod.c:397: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fragstats.c:337: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fragstats.c:337: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fragstats.c:493: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fragstats.c:527: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fragstats.c:542: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fragstats.c:555: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:265: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:265: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:266: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:266: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:267: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:267: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:280: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:301: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:320: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:360: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:387: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:491: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:496: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:752: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:762: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:821: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:828: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:849: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:861: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:864: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:867: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:887: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:898: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:923: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:924: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:925: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:926: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:927: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:931: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:949: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:957: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:959: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1017: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1102: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:1123: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:1127: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:1266: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1269: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1276: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1397: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1402: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1410: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1483: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:1570: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1576: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1582: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1589: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1609: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1626: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1632: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1698: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1701: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:1704: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3056: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3058: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3070: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3072: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3082: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3084: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3096: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3098: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3119: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3121: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3134: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3136: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3158: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3160: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3172: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3174: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3190: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3192: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3196: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3202: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3204: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3245: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3264: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3282: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3289: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3292: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../fs.c:3346: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../fs.c:3376: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_draw.c:229: [1] (buffer) fgetc: Check buffer boundaries if used in a loop.
- ../../gl_draw.c:289: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_draw.c:484: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_draw.c:485: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_draw.c:1894: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_md3.c:420: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_md3.c:428: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_model.c:216: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_model.c:335: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_model.c:414: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:415: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:419: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:429: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:563: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:888: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_model.c:901: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_model.c:1359: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1528: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1532: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1571: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1602: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1796: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1800: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_model.c:1841: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_ngraph.c:104: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_ngraph.c:198: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_ngraph.c:210: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_ngraph.c:211: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_ngraph.c:211: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_ngraph.c:211: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_ngraph.c:211: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_texture.c:606: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_texture.c:622: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../gl_texture.c:637: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_texture.c:687: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_texture.c:705: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_texture.c:719: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_texture.c:736: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../gl_warp.c:561: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hash.c:189: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hash.c:190: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hash.c:204: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hash.c:205: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../help.c:120: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../help.c:120: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../help.c:164: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../help.c:192: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../host.c:153: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:217: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../host.c:235: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:263: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:335: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:465: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../host.c:592: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:598: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:608: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../host.c:676: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud.c:137: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud.c:189: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:193: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:824: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:824: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:824: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:1080: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud.c:1140: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:1144: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud.c:1174: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud.c:1333: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:247: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:249: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:254: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:257: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:280: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:284: [1] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused). Risk is low because the source is a constant character.
- ../../hud_common.c:288: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:291: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:330: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:333: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:335: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:340: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:343: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:399: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:410: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:564: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:1737: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:1738: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:1755: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:1756: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:1760: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:1767: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:1769: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:1955: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:2700: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:2702: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:2719: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:2720: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:3108: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:3138: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:3293: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:3301: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:3698: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:3969: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:3972: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:3975: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:3980: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:3986: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4033: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4042: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4046: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4049: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4054: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4058: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4062: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4065: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4070: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4080: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../hud_common.c:4082: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:4131: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:4131: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:4904: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:5463: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_common.c:5790: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_editor.c:256: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_editor.c:309: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_editor.c:1660: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../hud_editor.c:2182: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../image.c:850: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../image.c:950: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../image.c:1358: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../image.c:1472: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../image.c:1566: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../image.c:2045: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../image.c:2199: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../in_win.c:851: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../in_win.c:851: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../in_win.c:855: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../in_win.c:963: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keymap.c:336: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keymap.c:427: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../keymap.c:606: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keymap.c:618: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keymap.c:626: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keymap.c:675: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../keys.c:332: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:349: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:412: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:516: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:520: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:582: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:591: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:602: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:645: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:647: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:672: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../keys.c:1389: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../keys.c:1639: [1] (buffer) fgetc: Check buffer boundaries if used in a loop.
- ../../keys.c:1990: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../keys.c:2001: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../keys.c:2033: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../linux_glimp.c:254: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../linux_glimp.c:452: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../linux_glimp.c:459: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../linux_glimp.c:549: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../linux_glimp.c:1570: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../linux_glimp.c:1571: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../logging.c:272: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../match_tools.c:169: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:171: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:398: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:400: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:410: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:412: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:545: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../match_tools.c:730: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../menu.c:202: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu.c:436: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu.c:991: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../menu.c:995: [1] (buffer) fscanf: it's unclear if the %s limit in the format string is small enough. Check that the limit is sufficiently small, or use a different input function.
- ../../menu.c:998: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../menu_demo.c:429: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_demo.c:439: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_demo.c:492: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../menu_demo.c:493: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../menu_demo.c:779: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_demo.c:780: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_demo.c:792: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_mp3player.c:37: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_mp3player.c:63: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_mp3player.c:87: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../menu_mp3player.c:89: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../menu_mp3player.c:425: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../modules.c:123: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../movie.c:198: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../movie.c:273: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../movie.c:280: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../movie.c:368: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_mpd.c:403: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mp3_player.c:138: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mp3_player.c:187: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mp3_winamp.c:97: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:107: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:137: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:142: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:199: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:200: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:343: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mp3_winamp.c:356: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_winamp.c:430: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mp3_xmms2.c:226: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_autotrack.c:90: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_autotrack.c:391: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_autotrack.c:401: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_autotrack.c:411: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_autotrack.c:421: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_autotrack.c:436: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_utils.c:279: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_utils.c:283: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_utils.c:300: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_utils.c:1062: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_utils.c:1084: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_utils.c:1105: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_utils.c:1126: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_xmlstats.c:37: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../mvd_xmlstats.c:38: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../mvd_xmlstats.c:40: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../net.c:97: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../net.c:105: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../net.c:130: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../net_chan.c:140: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../parser.c:173: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../parser.c:179: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../parser.c:185: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../parser.c:201: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../parser.c:201: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../parser.c:502: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:267: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:268: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:325: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:654: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:655: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:799: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_cmds.c:801: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_cmds.c:803: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:824: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_cmds.c:1025: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:1227: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:1238: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:1354: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_cmds.c:1358: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_cmds.c:1410: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_cmds.c:1602: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:1698: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_cmds.c:1699: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:197: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:200: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:204: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:208: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:211: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:214: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:217: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:220: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:223: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:241: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:244: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:248: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:252: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:255: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:258: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:261: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:264: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:282: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:285: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:288: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:304: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:306: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_edict.c:308: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:331: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:346: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:370: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:528: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../pr_edict.c:898: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../pr_exec.c:140: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../q_shared.c:162: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../q_shared.c:164: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../q_shared.c:246: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../q_shared.c:263: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../q_shared.c:292: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../q_shared.c:320: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../q_shared.c:831: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../qtv.c:54: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../qtv.c:174: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../qtv.c:192: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../qtv.c:194: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../qtv.c:195: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../r_draw.c:157: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../r_draw.c:158: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../r_draw.c:790: [1] (buffer) fgetc: Check buffer boundaries if used in a loop.
- ../../r_misc.c:234: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../r_misc.c:366: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../r_misc.c:378: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../r_misc.c:379: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../r_misc.c:379: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../r_misc.c:379: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../r_misc.c:379: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../r_model.c:911: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../r_part.c:276: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:691: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:758: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:970: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:972: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sbar.c:974: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sbar.c:1004: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1006: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sbar.c:1008: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sbar.c:1042: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1045: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1062: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1067: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sbar.c:1284: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1292: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1295: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1305: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1309: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1311: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sbar.c:1316: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1321: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1361: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1366: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1368: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1381: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1383: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1505: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1513: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1517: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1601: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sbar.c:1662: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../settings_page.c:84: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../settings_page.c:102: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../settings_page.c:113: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../settings_page.c:115: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../settings_page.c:137: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../settings_page.c:236: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../settings_page.c:363: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../settings_page.c:518: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../settings_page.c:559: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../settings_page.c:559: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../settings_page.c:563: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sha1.c:152: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sha1.c:161: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sha1.c:173: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../skin.c:90: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../skin.c:318: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../skin.c:340: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../skin.c:470: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../snd_dma.c:276: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../snd_mem.c:233: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../snd_ov.c:147: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../stats_grid.c:156: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../stats_grid.c:330: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:61: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_ccmds.c:118: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_ccmds.c:172: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:174: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:265: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:270: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:308: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:353: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:537: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_ccmds.c:540: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:541: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_ccmds.c:542: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_init.c:282: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_main.c:250: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:348: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_main.c:351: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:393: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_main.c:394: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:611: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:810: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_main.c:836: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:1167: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_main.c:1222: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:1245: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:1256: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_main.c:1263: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_main.c:1288: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_master.c:78: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_master.c:86: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_master.c:95: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_master.c:101: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_save.c:40: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_save.c:41: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_save.c:42: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_save.c:90: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_save.c:141: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_save.c:190: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_save.c:191: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_save.c:198: [1] (buffer) fgetc: Check buffer boundaries if used in a loop.
- ../../sv_send.c:48: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_send.c:58: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_send.c:58: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_send.c:83: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_sys_unix.c:162: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../sv_sys_unix.c:218: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../sv_user.c:172: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:172: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:374: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:690: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:858: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:874: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:905: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_user.c:907: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_user.c:909: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_user.c:943: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sv_user.c:1051: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sv_user.c:1053: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_linux.c:189: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../sys_linux.c:220: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../sys_linux.c:341: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../sys_linux.c:379: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_linux.c:448: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_linux.c:462: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_linux.c:466: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_linux.c:472: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_linux.c:483: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_linux.c:512: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_linux.c:513: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_linux.c:525: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_linux.c:546: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_linux.c:552: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_linux.c:557: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_linux.c:603: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_linux.c:613: [1] (access) umask: Ensure that umask is given most restrictive possible setting (e.g., 066 or 077).
- ../../sys_linux.c:615: [1] (access) umask: Ensure that umask is given most restrictive possible setting (e.g., 066 or 077).
- ../../sys_linux.c:619: [1] (access) umask: Ensure that umask is given most restrictive possible setting (e.g., 066 or 077).
- ../../sys_linux.c:661: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_mac.c:145: [1] (access) umask: Ensure that umask is given most restrictive possible setting (e.g., 066 or 077).
- ../../sys_mac.c:168: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../sys_mac.c:208: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_mac.c:209: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_mac.c:221: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_mac.c:242: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_mac.c:248: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_mac.c:253: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_mac.c:408: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_mac.c:423: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../sys_mac.c:1126: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_mac.c:1144: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_mac.c:1249: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_mac.c:1347: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../sys_mac.c:1375: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_mac.c:1444: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_mac.c:1458: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_mac.c:1462: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_mac.c:1468: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../sys_mac.c:1479: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:217: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_win.c:218: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:226: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_win.c:231: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:251: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_win.c:259: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../sys_win.c:357: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:488: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:707: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:1088: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../sys_win.c:1217: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:158: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:169: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:175: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:181: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:187: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:193: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:199: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:205: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:211: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:238: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:271: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:306: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:310: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:314: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:318: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:330: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:337: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:343: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:349: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:509: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:605: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:617: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:619: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:683: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:793: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:795: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:797: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:806: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:808: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:810: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:872: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:890: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:893: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:906: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:912: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:914: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:917: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:976: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:988: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1000: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1003: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1016: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1028: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1031: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1167: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1169: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1175: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1177: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1185: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1195: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1198: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1245: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1248: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1256: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1294: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1726: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1726: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1731: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1859: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1867: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1867: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1873: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1888: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:1893: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:1990: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2100: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2105: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2108: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2109: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2293: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2300: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2426: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2428: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:2710: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../teamplay.c:3115: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:3120: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../teamplay.c:3123: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../textencoding.c:41: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../textencoding.c:127: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../textencoding.c:137: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../tp_msgs.c:94: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../tp_msgs.c:105: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../tp_msgs.c:111: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../tp_triggers.c:157: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../tp_triggers.c:286: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../tp_triggers.c:301: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../tp_triggers.c:697: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../tp_triggers.c:725: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../tp_triggers.c:757: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../tp_triggers.c:863: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../tr_init.c:220: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:52: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:66: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:169: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:176: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:194: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:199: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:256: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:329: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:356: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:471: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:504: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:531: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:539: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:608: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:609: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../utils.c:661: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:893: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:937: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:976: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:1011: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:1079: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../utils.c:1134: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../version.c:88: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:112: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:118: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:124: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:131: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:144: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:161: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:173: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:181: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:189: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_doomwad.c:197: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_gzip.c:242: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_os.c:127: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_os.c:170: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_os.c:210: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_os.c:227: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vfs_os.c:231: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_os.c:269: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_pak.c:102: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_pak.c:114: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_pak.c:119: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_pak.c:334: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_pak.c:379: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_tar.c:116: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../vfs_tar.c:169: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vfs_tar.c:207: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_tar.c:222: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_tar.c:229: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_tar.c:394: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vfs_zip.c:179: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_zip.c:203: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_zip.c:205: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vfs_zip.c:206: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vid_common_gl.c:107: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vid_glx.c:482: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vid_glx.c:586: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../vid_glx.c:905: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers.
- ../../vid_glx.c:963: [1] (buffer) read: Check buffer boundaries if used in a loop.
- ../../vid_glx.c:965: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Use nanosleep(2) or setitimer(2) instead.
- ../../vid_mac.c:913: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vid_win.c:337: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:339: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:910: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:912: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:914: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:930: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:932: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:934: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:2610: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:2619: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vid_win.c:2626: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:102: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:290: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:291: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:293: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:296: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:297: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:301: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:302: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:306: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:307: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:311: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:312: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_stuff.c:316: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_stuff.c:317: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_tracker.c:170: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:175: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../vx_tracker.c:259: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:261: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:271: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:273: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:283: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:285: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:287: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:300: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:302: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:312: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:314: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:316: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:326: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:328: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:338: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:340: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:349: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:356: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:363: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:410: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:412: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:426: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:428: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:430: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:432: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:437: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:439: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:441: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:454: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:456: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../vx_tracker.c:592: [1] (port) snprintf: On some very old systems, snprintf is incorrectly implemented and permits buffer overflows; there are also incompatible standard definitions of it. Check it during installation, or use something else.
- ../../xsd.c:59: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd.c:62: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd.c:63: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd.c:87: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd.c:88: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd.c:115: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd.c:118: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd_command.c:115: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../xsd_variable.c:164: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).
- ../../zone2.c:596: [1] (buffer) strlen: Does not handle strings that are not \0-terminated (it could cause a crash if unprotected).

Saving hitlist to lists/flaws_base.list