Flawfinder version 1.27, (C) 2001-2004 David A. Wheeler.
Number of dangerous functions in C/C++ ruleset: 160
upp/uppsrc/Core/App.cpp:47:  [5] (race) readlink:
  This accepts filename arguments; if an attacker can move those files
  or change the link content, a race condition results.  Also, it does not
  terminate with ASCII NUL. Reconsider approach. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1137:  [5] (race) chmod:
  This accepts filename arguments; if an attacker can move those files,
  a race condition results. . Use fchmod( ) instead. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1143:  [5] (race) chown:
  This accepts filename arguments; if an attacker can move those files,
  a race condition results. . Use fchown( ) instead. 
upp/bazaar/SysExec/SysExec.cpp:131:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/SysExec/SysExec.cpp:163:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/SystemLog/SystemLog.cpp:163:  [4] (format) syslog:
  If syslog's format strings can be influenced by an attacker, they can
  be exploited. Use a constant format string for syslog. 
upp/bazaar/UnitTest++/AssertException.cpp:10:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTest++/AssertException.cpp:11:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTest++/MemoryOutStream.cpp:32:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/bazaar/UnitTest++/MemoryOutStream.cpp:73:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/bazaar/UnitTest++/MemoryOutStream.cpp:131:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTest++/TestReporterStdout.cpp:15:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/bazaar/UnitTestTest/RecordingReporter.h:39:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:40:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:46:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:48:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:49:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:50:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:56:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/RecordingReporter.h:57:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/TestDeferredTestReporter.cpp:95:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/bazaar/UnitTestTest/TestDeferredTestReporter.cpp:97:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/benchmarks/AllocMT/Chris.cpp:77:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/benchmarks/AllocMT/Chris2.cpp:16:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/BuildAll/BuildAll.cpp:37:  [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. 
upp/uppsrc/Core/App.cpp:33:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/App.cpp:341:  [4] (shell) ShellExecute:
  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. 
upp/uppsrc/Core/App.cpp:348:  [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. 
upp/uppsrc/Core/App.cpp:349:  [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. 
upp/uppsrc/Core/CharSet.cpp:798:  [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. 
upp/uppsrc/Core/CharSet.cpp:1044:  [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. 
upp/uppsrc/Core/Debug.cpp:19:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Debug.cpp:26:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Debug.cpp:38:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Debug.cpp:51:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/Core/Debug.cpp:54:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/Core/Debug.cpp:55:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/Core/Debug.cpp:114:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Debug.cpp:123:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/Core/Debug.cpp:236:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/Core/Debug.cpp:407:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Format.cpp:12:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/Core/Format.cpp:557:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/Core/Format.cpp:630:  [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. 
upp/uppsrc/Core/Format.cpp:633:  [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. 
upp/uppsrc/Core/Format.cpp:641:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/Core/Format.cpp:653:  [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. 
upp/uppsrc/Core/Format.cpp:656:  [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. 
upp/uppsrc/Core/Format.cpp:664:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/Core/LocalProcess.cpp:205:  [4] (shell) execv:
  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. 
upp/uppsrc/Core/Log.cpp:68:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Log.cpp:69:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Log.cpp:140:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Log.cpp:142:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Log.cpp:146:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/Core/Path.cpp:1002:  [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. 
upp/uppsrc/Core/Path.cpp:1005:  [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. 
upp/uppsrc/Core/Path.cpp:1008:  [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. 
upp/uppsrc/Core/Path.cpp:1008:  [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. 
upp/uppsrc/Core/Util.cpp:90:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/Core/Util.cpp:160:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/Util.cpp:785:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/Core/Util.cpp:787:  [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. 
upp/uppsrc/Core/heapdbg.cpp:49:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/heapdbg.cpp:50:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/Core/t.cpp:237:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/Core/t.cpp:349:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/CppBase/Base.cpp:10:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/CppBase.h:232:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/CppBase.h:279:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:203:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:1125:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:1148:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:1257:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:1358:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:1391:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CppBase/Parser.cpp:1435:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/CtrlLib/PrinterJob.cpp:154:  [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. 
upp/uppsrc/CtrlLib/Update.cpp:128:  [4] (shell) WinExec:
  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. 
upp/uppsrc/CtrlLib/Update.cpp:144:  [4] (shell) WinExec:
  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. 
upp/uppsrc/CtrlLib/Update.cpp:159:  [4] (shell) WinExec:
  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. 
upp/uppsrc/Docedit/DocItem.cpp:285:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/Draw/DrawTextWin32.cpp:319:  [4] (buffer) wcscpy:
  Does not check for buffer overflows when copying to destination.
  Consider using a function version that stops copying at the end of the
  buffer. 
upp/uppsrc/GridCtrl/GridUtils.cpp:15:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/GridCtrl/GridUtils.cpp:25:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/GridCtrl/GridUtils.cpp:38:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/GridCtrl/GridUtils.cpp:56:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/Oracle/Oci8.cpp:30:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/TCore/datafile.cpp:23:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/TCore/util.cpp:1201:  [4] (shell) WinExec:
  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. 
upp/uppsrc/Updater/Updater.cpp:22:  [4] (shell) WinExec:
  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. 
upp/uppsrc/docpp/Parser.cpp:45:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:587:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:598:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:668:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:671:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:718:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:749:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:773:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/Parser.cpp:778:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/docpp.h:135:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/docpp/docpp.h:158:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Annotations.cpp:170:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Annotations.cpp:180:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Build.cpp:863:  [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. 
upp/uppsrc/ide/Debuggers/Sym.cpp:62:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/ide/Debuggers/Sym.cpp:254:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/ide/Install.cpp:57:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/ide/Thisbacks.cpp:21:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:64:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:79:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:79:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:108:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:108:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:112:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:119:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:119:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Thisbacks.cpp:121:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/ide/Uninstall.cpp:60:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/ide/Valgrind.cpp:7:  [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. 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp:100:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:661:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1195:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1697:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1803:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:344:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:381:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:503:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:514:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzlib.c:1439:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:103:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:111:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:113:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:115:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:117:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:119:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/bz2/lib/bzlib_private.h:121:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:147:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:337:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:606:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:633:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:640:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:959:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1103:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1143:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1160:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1189:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1315:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1340:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1382:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1385:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1402:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:403:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/jpg/lib/jerror.c:193:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/jpg/lib/jerror.c:195:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/jpg/lib/jmemmac.c:240:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/jpg/lib/jmemmac.c:241:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/jpg/lib/jmemname.c:102:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/jpg/lib/jmemname.c:129:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/jpg/lib/jmemname.c:130:  [4] (tmpfile) mktemp:
  Temporary file race condition. 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:456:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:466:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:602:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:607:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:639:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:664:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:689:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:693:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:697:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:705:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:105:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:325:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:1085:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:1097:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:1098:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/ndisasm/lib/ndisasm.c:69:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/ndisasm/lib/ndisasm.c:200:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/pcre/lib/pcre_internal.h:64:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/png/lib/png.h:2488:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/png/lib/png.h:2494:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/png/lib/png.h:2500:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/png/lib/pngconf.h:1444:  [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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1445:  [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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1446:  [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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1448:  [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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1449:  [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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1450:  [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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1458:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/png/lib/pngconf.h:1459:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/png/lib/pngconf.h:1461:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/png/lib/pngconf.h:1463:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/png/lib/pngtest.c:35:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/png/lib/pngwutil.c:1615:  [4] (format) swprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/png/lib/pngwutil.c:1619:  [4] (format) swprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/sqlite3/lib/btreeInt.h:491:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:310:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:2778:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2484:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2519:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2535:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:32:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1178:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1972:  [4] (race) access:
  This usually indicates a security flaw.  If an attacker can change
  anything along the path between the call to access() and the file's actual
  use (e.g., by moving files), the attacker can exploit the race
  condition. Set up the correct permissions (e.g., using setuid()) and try to
  open the file directly. 
upp/uppsrc/plugin/sqlite3/lib/sqlite3ext.h:130:  [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. 
upp/uppsrc/plugin/sqlite3/lib/sqlite3ext.h:295:  [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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:725:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:504:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:516:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_apple.c:170:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/tif/lib/tif_apple.c:261:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_apple.c:271:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_atari.c:230:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_atari.c:240:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_compress.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). 
upp/uppsrc/plugin/tif/lib/tif_extension.c:107:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:102:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:113:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:129:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:136:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:146:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:152:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:161:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:169:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:174:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:182:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:298:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:330:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:341:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:363:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:372:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:377:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:385:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:395:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:400:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:411:  [4] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. 
upp/uppsrc/plugin/tif/lib/tif_msdos.c:166:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_msdos.c:176:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_open.c:168:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/tif/lib/tif_unix.c:280:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_unix.c:290:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:312:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:327:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_win3.c:207:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/tif/lib/tif_win3.c:208:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/tif/lib/tif_win3.c:220:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/tif/lib/tif_win3.c:221:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:349:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:351:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:359:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:377:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:379:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:386:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/z/lib/gzio.c:109:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/z/lib/gzio.c:537:  [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. 
upp/uppsrc/plugin/z/lib/gzio.c:539:  [4] (format) vsprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/z/lib/gzio.c:560:  [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. 
upp/uppsrc/plugin/z/lib/gzio.c:563:  [4] (format) sprintf:
  Potential format string problem. Make format string constant. 
upp/uppsrc/plugin/z/lib/gzio.c:876:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/z/lib/gzio.c:878:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/z/lib/minigzip.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). 
upp/uppsrc/plugin/z/lib/minigzip.c:204:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/z/lib/minigzip.c:234:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination.
  Consider using strncpy or strlcpy (warning, strncpy is easily misused). 
upp/uppsrc/plugin/z/lib/minigzip.c:243:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/uppsrc/plugin/z/lib/zutil.h:195:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/z/lib/zutil.h:196:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/z/lib/zutil.h:197:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/z/lib/zutil.h:198:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/plugin/z/lib/zutil.h:199:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be
  exploited. Use a constant for the format specification. 
upp/uppsrc/umk/umk.cpp:30:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused). 
upp/bazaar/SysExec/SysExec.cpp:19:  [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. 
upp/uppsrc/Core/App.cpp:11:  [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. 
upp/uppsrc/Core/Debug.cpp:37:  [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. 
upp/uppsrc/Core/Dli.cpp:109:  [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. 
upp/uppsrc/Core/Dli.cpp:111:  [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. 
upp/uppsrc/Core/LocalProcess.cpp:96:  [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. 
upp/uppsrc/Core/LocalProcess.cpp:96:  [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. 
upp/uppsrc/Core/LocalProcess.cpp:158:  [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. 
upp/uppsrc/Core/Log.cpp:141:  [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. 
upp/uppsrc/Core/Mt.cpp:288:  [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. 
upp/uppsrc/Core/Mt.cpp:306:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Core/Mt.cpp:342:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Core/Mt.h:194:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Core/Mt.h:197:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Core/Mt.h:199:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Core/Mt.h:201:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Core/Path.cpp:255:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/Core/Path.h:202:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/CtrlCore/Win32Wnd.cpp:273:  [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. 
upp/uppsrc/CtrlLib/PrinterJob.cpp:147:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/CtrlLib/PrinterJob.cpp:148:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/Draw/DrawTextWin32.cpp:68:  [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. 
upp/uppsrc/Draw/ImageWin32.cpp:189:  [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. 
upp/uppsrc/RichEdit/Speller.cpp:140:  [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. 
upp/uppsrc/RichEdit/Speller.cpp:142:  [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. 
upp/uppsrc/TCore/datatest.cpp:24:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/TCore/datatest.cpp:40:  [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. 
upp/uppsrc/TCore/datatest.cpp:69:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/TCore/datatest.cpp:95:  [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. 
upp/uppsrc/TCore/datatest.cpp:456:  [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. 
upp/uppsrc/TCore/datatest.cpp:565:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/TCore/datatest.cpp:650:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/TCore/util.cpp:1133:  [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. 
upp/uppsrc/Web/TServ/tserv.cpp:532:  [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. 
upp/uppsrc/Web/TServ/tserv.cpp:532:  [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. 
upp/uppsrc/Web/sproc.cpp:161:  [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. 
upp/uppsrc/Web/sproc.cpp:161:  [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. 
upp/uppsrc/Web/sproc.cpp:221:  [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. 
upp/uppsrc/Web/wisapi/wisapi.cpp:59:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/Web/wisapi/wisapi.cpp:62:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/coff/lib.cpp:94:  [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. 
upp/uppsrc/coff/lib.h:24:  [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. 
upp/uppsrc/coff/uar/lib.cpp:174:  [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. 
upp/uppsrc/coff/uld/linkjob.cpp:751:  [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. 
upp/uppsrc/coff/uld/linkjob.cpp:772:  [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. 
upp/uppsrc/coff/uld/obj.h:328:  [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. 
upp/uppsrc/ide/Builders/JavaBuilder.cpp:282:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/ide/Host.cpp:201:  [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. 
upp/uppsrc/ide/Host.cpp:201:  [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. 
upp/uppsrc/ide/Install.cpp:58:  [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. 
upp/uppsrc/ide/Install.cpp:58:  [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. 
upp/uppsrc/ide/Install.cpp:316:  [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. 
upp/uppsrc/ide/Uninstall.cpp:61:  [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. 
upp/uppsrc/ide/Uninstall.cpp:61:  [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. 
upp/uppsrc/ide/Valgrind.cpp:32:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/ide/idewin.cpp:738:  [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. 
upp/uppsrc/ide/idewin.cpp:738:  [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. 
upp/uppsrc/ide/idewin.cpp:780:  [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. 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp:100:  [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. 
upp/uppsrc/plugin/astyle/ASFormatter.cpp:131:  [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. 
upp/uppsrc/plugin/astyle/ASFormatter.cpp:136:  [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. 
upp/uppsrc/plugin/astyle/astyle_main.cpp:979:  [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. 
upp/uppsrc/plugin/astyle/astyle_main.cpp:985:  [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. 
upp/uppsrc/plugin/astyle/astyle_main.cpp:991:  [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. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1821:  [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. 
upp/uppsrc/plugin/bz2/lib/dlltest.c:32:  [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. 
upp/uppsrc/plugin/bz2/lib/spewG.c:26:  [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. 
upp/uppsrc/plugin/bz2/lib/spewG.c:29:  [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. 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:50:  [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. 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:139:  [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. 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:140:  [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. 
upp/uppsrc/plugin/jpg/lib/jmemmgr.c:35:  [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. 
upp/uppsrc/plugin/jpg/lib/jmemmgr.c:1162:  [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. 
upp/uppsrc/plugin/png/lib/example.c:240:  [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. 
upp/uppsrc/plugin/sqlite3/lib/mutex_w32.c:109:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/plugin/sqlite3/lib/mutex_w32.c:121:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/plugin/sqlite3/lib/mutex_w32.c:166:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:1617:  [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. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1788:  [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. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1793:  [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. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1800:  [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. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1801:  [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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1252:  [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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1254:  [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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1254:  [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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1255:  [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. 
upp/uppsrc/plugin/tif/lib/mkg3states.c:385:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer
  overflows . Check implementation on installation, or limit the size of all
  string inputs. 
upp/uppsrc/plugin/tif/tifupp.cpp:770:  [3] (tmpfile) GetTempFileName:
  Temporary file race condition in certain cases (e.g., if run as SYSTEM
  in many versions of Windows). 
upp/uppsrc/umk/umk.cpp:32:  [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. 
upp/uppsrc/umk/umk.cpp:32:  [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. 
upp/bazaar/DockCtrlExample/main.cpp:160:  [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?. 
upp/bazaar/DockCtrlExample/main.cpp:182:  [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?. 
upp/bazaar/Signals/Signals.cpp:31:  [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). 
upp/bazaar/Signals/Signals.cpp:46:  [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?. 
upp/bazaar/Signals/Signals.cpp:250:  [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). 
upp/bazaar/SvnLib/SvnLib.cpp:251:  [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). 
upp/bazaar/SvnLib/SvnLib.cpp:284:  [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). 
upp/bazaar/SvnLib/SvnLib.cpp:336:  [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). 
upp/bazaar/SvnLib/SvnLib.cpp:402:  [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). 
upp/bazaar/SvnLib/SvnLib.cpp:407:  [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). 
upp/bazaar/SysExec/SysExec.cpp:10:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/SysExec/SysExec.cpp:38:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/bazaar/SysExec/SysExec.cpp:39:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/bazaar/SysExec/SysExec.cpp:46:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/bazaar/SysExec/SysExec.cpp:48:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/bazaar/SysExec/SysExec.cpp:191:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/bazaar/SysExec/SysExec.cpp:198:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/bazaar/SystemLog/SystemLog.cpp:165:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTest++/AssertException.h:21:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTest++/AssertException.h:22:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTest++/MemoryOutStream.cpp: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. 
upp/bazaar/UnitTestTest/RecordingReporter.h:70:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTestTest/RecordingReporter.h:71:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTestTest/RecordingReporter.h: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. 
upp/bazaar/UnitTestTest/RecordingReporter.h:76:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTestTest/RecordingReporter.h: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. 
upp/bazaar/UnitTestTest/RecordingReporter.h:78:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/bazaar/UnitTestTest/RecordingReporter.h: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. 
upp/bazaar/UnitTestTest/RecordingReporter.h: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. 
upp/bazaar/UnitTestTest/TestDeferredTestReporter.cpp: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. 
upp/bazaar/maxpdf_frontend/maxpdf_frontend.cpp:187:  [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). 
upp/bazaar/maxpdf_frontend/maxpdf_frontend.cpp:257:  [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). 
upp/benchmarks/AllocMT/Chris.cpp:104:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/benchmarks/AllocMT/Chris.cpp:245:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/benchmarks/AllocMT/Chris2.cpp: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. 
upp/examples/AddressBook/AddressBook.cpp:63:  [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?. 
upp/examples/AddressBookXML/AddressBook.cpp:60:  [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?. 
upp/examples/AddressBookXML2/AddressBook.cpp:67:  [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?. 
upp/examples/BlueBar/UWord.cpp:67:  [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?. 
upp/examples/OleCalc/calc_idl.cpp: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. 
upp/examples/OleCalc/calc_idl.cpp:148:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/examples/OleCalc/calc_p.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. 
upp/examples/OleCalc/calc_p.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. 
upp/examples/OleCalc/calc_p.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. 
upp/examples/OleCalc/calc_p.c:507:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/examples/UWord/UWord.cpp:66:  [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?. 
upp/reference/ColumnListDnD/main.cpp:25:  [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). 
upp/reference/Log/log.cpp: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. 
upp/reference/VirtualArray/main.cpp:7:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/reference/VirtualArray/main.cpp:12:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/tutorial/Core02/main.cpp:7:  [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.
upp/tutorial/Image06/main.cpp: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. 
upp/uppsrc/AnalyzeMap/Analyze.cpp: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. 
upp/uppsrc/CodeEditor/CodeEditor.cpp:611:  [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). 
upp/uppsrc/CodeEditor/Highlight.cpp: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. 
upp/uppsrc/CodeEditor/Highlight.cpp: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. 
upp/uppsrc/Core/App.cpp: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. 
upp/uppsrc/Core/App.cpp: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. 
upp/uppsrc/Core/App.cpp:41:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/App.cpp:43:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/App.cpp:45:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/App.cpp:240:  [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). 
upp/uppsrc/Core/App.cpp:363:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/App.cpp: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. 
upp/uppsrc/Core/BlockStream.cpp:157:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:162:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:173:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:191:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:198:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:203:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:212:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/BlockStream.cpp:409:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/BlockStream.cpp:470:  [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?. 
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp:42:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp:122:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Debug.cpp:144:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp:200:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Debug.cpp:201:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp:352:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Debug.cpp:367:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Debug.cpp:370:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Debug.cpp:375:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp: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. 
upp/uppsrc/Core/Debug.cpp:447:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Diag.h:15:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Diag.h:16:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Dli.cpp: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. 
upp/uppsrc/Core/Format.cpp:25:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Format.cpp:57:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Format.cpp: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. 
upp/uppsrc/Core/Format.cpp: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. 
upp/uppsrc/Core/Format.cpp:157:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Format.cpp: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. 
upp/uppsrc/Core/Format.cpp: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. 
upp/uppsrc/Core/Format.cpp:651:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Hash.h:8:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Lang.cpp: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. 
upp/uppsrc/Core/Lang.cpp:104:  [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). 
upp/uppsrc/Core/Lang.cpp: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. 
upp/uppsrc/Core/Lang.cpp: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. 
upp/uppsrc/Core/Lang.cpp:213:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Lang.cpp:458:  [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). 
upp/uppsrc/Core/Lang.cpp:469:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/LocalProcess.cpp:95:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/LocalProcess.cpp:125:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/LocalProcess.cpp:334:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/LocalProcess.cpp: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. 
upp/uppsrc/Core/Log.cpp:8:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Log.cpp:70:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/Core/Log.cpp:75:  [2] (buffer) wchar_t:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Log.cpp:90:  [2] (buffer) wchar_t:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Log.cpp:116:  [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?. 
upp/uppsrc/Core/Log.cpp: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. 
upp/uppsrc/Core/Log.cpp: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. 
upp/uppsrc/Core/Log.cpp: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. 
upp/uppsrc/Core/Log.cpp:153:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Log.cpp:160:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/MD5.cpp: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. 
upp/uppsrc/Core/MD5.cpp: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. 
upp/uppsrc/Core/MD5.cpp: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. 
upp/uppsrc/Core/MD5.cpp:303:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Other.h:178:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Path.cpp:205:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Path.cpp: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. 
upp/uppsrc/Core/Path.cpp: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. 
upp/uppsrc/Core/Path.cpp:288:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Path.cpp:995:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Path.cpp:1002:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Random.cpp:163:  [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?. 
upp/uppsrc/Core/SHA1.cpp:122:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/SHA1.cpp:128:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.cpp:845:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.cpp:859:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.cpp:911:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.cpp:921:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.cpp:1121:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.cpp:1166:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Stream.cpp:1197:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Stream.cpp:1272:  [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?. 
upp/uppsrc/Core/Stream.cpp:1306:  [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?. 
upp/uppsrc/Core/Stream.h:85:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Stream.h:86:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:80:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:130:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:137:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:139:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:141:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:158:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:233:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:242:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:270:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:319:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:366:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:368:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:393:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.cpp:413:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/String.h: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. 
upp/uppsrc/Core/String.h:336:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/TimeDate.cpp:71:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/TimeDate.cpp: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. 
upp/uppsrc/Core/TimeDate.cpp: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. 
upp/uppsrc/Core/Topt.h:123:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Topt.h:128:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Topt.h:133:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Util.cpp: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. 
upp/uppsrc/Core/Util.cpp:598:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/Core/Util.cpp: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. 
upp/uppsrc/Core/Util.cpp:728:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/Util.cpp:783:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Util.cpp:784:  [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.
upp/uppsrc/Core/Util.h:88:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.cpp:22:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.hpp:247:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.hpp:248:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.hpp:295:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.hpp:599:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.hpp:601:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Vcont.hpp:602:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:50:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:57:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:59:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:61:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:111:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:125:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:135:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:302:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:304:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/WString.cpp:330:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Core/Win32Util.cpp: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. 
upp/uppsrc/Core/Win32Util.cpp:147:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/Win32Util.cpp: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. 
upp/uppsrc/Core/Win32Util.cpp: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. 
upp/uppsrc/Core/heapdbg.cpp:41:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/heapdbg.cpp: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. 
upp/uppsrc/Core/heapdbg.cpp:48:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Core/heapdbg.cpp: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. 
upp/uppsrc/Core/heapdbg.cpp:107:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/heapdbg.cpp: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. 
upp/uppsrc/Core/heapdbg.cpp:125:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Core/heapdbg.cpp: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. 
upp/uppsrc/Core/parser.cpp:419:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Crash/crash.cpp:63:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Crypto/BscF.cpp:126:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Crypto/BscF.cpp:144:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Crypto/Sha1.cpp:113:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Crypto/Sha1.cpp:118:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Crypto/Sha1.cpp:155:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Crypto/Sha1.cpp:161:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlCore/Win32Clip.cpp:71:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlCore/Win32Clip.cpp:340:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlCore/Win32Clip.cpp:341:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlCore/Win32DnD.cpp: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. 
upp/uppsrc/CtrlCore/Win32DnD.cpp:296:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlCore/Win32Proc.cpp: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. 
upp/uppsrc/CtrlCore/Win32Proc.cpp:286:  [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). 
upp/uppsrc/CtrlCore/Win32Wnd.cpp: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. 
upp/uppsrc/CtrlCore/X11App.cpp: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. 
upp/uppsrc/CtrlCore/X11App.cpp: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. 
upp/uppsrc/CtrlCore/X11Proc.cpp: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. 
upp/uppsrc/CtrlLib/AKeys.cpp:24:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/AKeys.cpp:40:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/ArrayCtrl.cpp:2358:  [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). 
upp/uppsrc/CtrlLib/ChGtk.cpp:625:  [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). 
upp/uppsrc/CtrlLib/ChGtk.cpp:1012:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/CtrlUtil.h: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. 
upp/uppsrc/CtrlLib/CtrlUtil.h: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. 
upp/uppsrc/CtrlLib/CtrlUtil.h:163:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/CtrlLib/CtrlUtil.h:165:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/CtrlLib/CtrlUtil.h:241:  [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?. 
upp/uppsrc/CtrlLib/DlgColor.cpp:1163:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/DocEdit.cpp:35:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/DropChoice.h:13:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move
  things around to create a race condition, control its ancestors, or change
  its contents?. 
upp/uppsrc/CtrlLib/PopupTable.cpp:14:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move
  things around to create a race condition, control its ancestors, or change
  its contents?. 
upp/uppsrc/CtrlLib/PopupTable.cpp:27:  [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?. 
upp/uppsrc/CtrlLib/PopupTable.cpp:99:  [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?. 
upp/uppsrc/CtrlLib/ToolTip.cpp:148:  [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?. 
upp/uppsrc/CtrlLib/ToolTip.cpp:162:  [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?. 
upp/uppsrc/CtrlLib/ToolTip.cpp:171:  [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?. 
upp/uppsrc/CtrlLib/TrayIconWin32.cpp:59:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/TrayIconWin32.cpp:73:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/TrayIconWin32.cpp:78:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/TrayIconX11.cpp:84:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:478:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:481:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:481:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:482:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:492:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:499:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:501:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:504:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:1712:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.cpp:1725:  [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?. 
upp/uppsrc/CtrlLib/TreeCtrl.h:387:  [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?. 
upp/uppsrc/CtrlLib/Update.cpp: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. 
upp/uppsrc/CtrlLib/Update.cpp: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. 
upp/uppsrc/CtrlLib/Win32.cpp:100:  [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?. 
upp/uppsrc/CtrlLib/Win32.cpp:114:  [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?. 
upp/uppsrc/CtrlLib/Win32.cpp:131:  [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?. 
upp/uppsrc/CtrlLib/Win32.cpp:145:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/CtrlLib/Win32.cpp:151:  [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?. 
upp/uppsrc/CtrlLib/Win32.cpp:158:  [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?. 
upp/uppsrc/CtrlLib/Win32.cpp:162:  [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?. 
upp/uppsrc/CtrlLib/Win32.cpp:167:  [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?. 
upp/uppsrc/Draw/Debug.cpp:9:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Draw/DrawUtil.cpp: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. 
upp/uppsrc/Draw/Image.cpp:55:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/Image.h:261:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Draw/ImageChOp.cpp:192:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageChOp.cpp:211:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageOp.cpp:146:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageOp.cpp:510:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Draw/ImageOp.cpp:511:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageOp.cpp:512:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageOp.cpp:612:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageWin32.cpp:205:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageWin32.cpp:304:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageWin32.cpp:364:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageWin32.cpp:571:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/ImageX11.cpp:389:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/Raster.cpp:90:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/Raster.cpp:139:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/Raster.cpp:146:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/Raster.cpp:154:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/RasterEncoder.cpp:69:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/RasterEncoder.cpp:80:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/RasterEncoder.cpp:130:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/RasterFormat.cpp:352:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/RasterWrite.cpp:325:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Draw/iml_source.h:43:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Geom/Ctrl/pathCtrl.cpp:1719:  [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?. 
upp/uppsrc/Geom/Ctrl/pathCtrl.cpp:1732:  [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?. 
upp/uppsrc/Geom/Draw/hrr.cpp:52:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Geom/Draw/hrr.cpp:343:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Geom/vecalg.cpp: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. 
upp/uppsrc/Geom/vecalg.cpp:113:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/GridCtrl/GridCtrl.cpp:7507:  [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?. 
upp/uppsrc/GridCtrl/GridCtrl.cpp:7614:  [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). 
upp/uppsrc/GridCtrl/GridCtrl.cpp:7667:  [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?. 
upp/uppsrc/GridCtrl/GridCtrl.h:48:  [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?. 
upp/uppsrc/GridCtrl/GridCtrl.h:58:  [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?. 
upp/uppsrc/GridCtrl/GridCtrl.h:110:  [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?. 
upp/uppsrc/GridCtrl/GridCtrl.h:114:  [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?. 
upp/uppsrc/GridCtrl/GridUtils.cpp:12:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/GridCtrl/GridUtils.cpp:22:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/GridCtrl/GridUtils.cpp: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. 
upp/uppsrc/GridCtrl/GridUtils.cpp: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. 
upp/uppsrc/HexView/HexView.cpp: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. 
upp/uppsrc/HexView/HexView.cpp: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. 
upp/uppsrc/HexView/HexView.cpp:114:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/HexView/HexView.cpp:120:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/HexView/HexView.cpp:157:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/IconDes/ImageOp.cpp:135:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/IconDes/ImageOp.cpp:136:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/IconDes/ImageOp.cpp:137:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/MySql/MySql.cpp:349:  [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). 
upp/uppsrc/MySql/MySql.cpp:349:  [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). 
upp/uppsrc/MySql/MySql.cpp:349:  [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). 
upp/uppsrc/MySql/MySql.cpp:363:  [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). 
upp/uppsrc/MySql/MySql.cpp:373:  [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). 
upp/uppsrc/MySql/MySql.cpp:374:  [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). 
upp/uppsrc/MySql/MySql.cpp:375:  [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). 
upp/uppsrc/Ole/util.cpp:29:  [2] (buffer) wchar_t:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/OleDB/OleDB.cpp:162:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/OleDB/OleDB.cpp:171:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Oracle/Oci7.cpp:223:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Oracle/Oci7.cpp:419:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Oracle/Oci8.cpp:269:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Oracle/contest.cpp: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. 
upp/uppsrc/PdfDraw/TTFStream.cpp:106:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:246:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:467:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:507:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:507:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:507:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:524:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:537:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:538:  [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). 
upp/uppsrc/PostgreSQL/PostgreSQL.cpp:539:  [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). 
upp/uppsrc/RichEdit/Speller.cpp:10:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/RichEdit/Speller.cpp: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. 
upp/uppsrc/RichEdit/Speller.cpp: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. 
upp/uppsrc/RichEdit/Speller.cpp:104:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/RichEdit/Speller.cpp:201:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/RichEdit/Table.cpp: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). 
upp/uppsrc/RichText/Format.cpp:200:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/RichText/ParseRTF.cpp:712:  [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). 
upp/uppsrc/Sql/SqlCase.cpp:20:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Sql/SqlCase.cpp:26:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Sql/SqlCase.cpp:197:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Sql/SqlCase.cpp:198:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/CalcNode.cpp:1142:  [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). 
upp/uppsrc/TCore/CalcNode.cpp:1156:  [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). 
upp/uppsrc/TCore/CalcNode.cpp:1157:  [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). 
upp/uppsrc/TCore/CalcNode.cpp:1164:  [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). 
upp/uppsrc/TCore/database.cpp:261:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:305:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:423:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:426:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:445:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:466:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp: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. 
upp/uppsrc/TCore/database.cpp:569:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:624:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/TCore/database.cpp:706:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:837:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:844:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:864:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/database.cpp:872:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/datafile.h: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. 
upp/uppsrc/TCore/nls_bw.hpp:492:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/TCore/nls_bw.hpp:677:  [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). 
upp/uppsrc/TCore/nls_bw.hpp:677:  [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). 
upp/uppsrc/TCore/util.cpp:300:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCore/util.cpp:1120:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/TCore/util.h:170:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCtrlLib/DocMgr.cpp:382:  [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?. 
upp/uppsrc/TCtrlLib/Help/DlgHelp.cpp:804:  [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?. 
upp/uppsrc/TCtrlLib/Help/DlgShot.cpp:368:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/TCtrlLib/OldTreeCtrl.cpp:624:  [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?. 
upp/uppsrc/TCtrlLib/OldTreeCtrl.h:42:  [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?. 
upp/uppsrc/TCtrlLib/OldTreeCtrl.h:76:  [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?. 
upp/uppsrc/VectorDes/VectorObj.cpp:1313:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Web/SSL/util.cpp:67:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/SSL/util.cpp: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. 
upp/uppsrc/Web/SSL/util.cpp: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. 
upp/uppsrc/Web/SSL/util.cpp:143:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/TServ/tserv.cpp:531:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/TServ/tserv.cpp:772:  [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). 
upp/uppsrc/Web/auth.cpp: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. 
upp/uppsrc/Web/md5.cpp:7:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Web/smtp.cpp: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. 
upp/uppsrc/Web/smtp.cpp: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. 
upp/uppsrc/Web/socket.cpp: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. 
upp/uppsrc/Web/socket.cpp:611:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Web/socket.cpp:632:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/sproc.cpp:160:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/sproc.cpp:188:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/sproc.cpp:396:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Web/sproc.cpp:421:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Web/util.cpp: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. 
upp/uppsrc/Web/util.cpp:186:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/Web/util.cpp:670:  [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). 
upp/uppsrc/Web/weblink/weblink.cpp: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. 
upp/uppsrc/Web/weblink/weblink.cpp:33:  [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.
upp/uppsrc/Web/weblink/weblink.cpp:71:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/Web/weblink/weblink.cpp:72:  [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.
upp/uppsrc/Web/weblink/weblink.cpp: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. 
upp/uppsrc/Web/weblink/weblink.cpp:142:  [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.
upp/uppsrc/Web/wisapi/wisapi.cpp:174:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/wisapi/wisapi.cpp:644:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/Web/wisapi/wisapi.cpp:1382:  [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.
upp/uppsrc/Web/wisapi/wisapicfg.cpp: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. 
upp/uppsrc/Web/wisapi/wisapicfg.cpp:121:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:193:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:237:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:269:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:277:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:407:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:417:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:422:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/binobj/binobj.cpp:426:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:120:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:122:  [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). 
upp/uppsrc/coff/lib.cpp:138:  [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). 
upp/uppsrc/coff/lib.cpp:147:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/coff/lib.cpp:148:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:259:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:266:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:269:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:272:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:274:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:285:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:291:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:296:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:301:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/coff/lib.cpp:302:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/coff/lib.cpp:309:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/coff/lib.cpp:310:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/coff/lib.cpp:314:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/coff/lib.cpp:315:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/coff/lib.cpp:327:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/lib.cpp:336:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/dump.cpp: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. 
upp/uppsrc/coff/uld/dump.cpp:161:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:791:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:793:  [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). 
upp/uppsrc/coff/uld/linkjob.cpp:805:  [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). 
upp/uppsrc/coff/uld/linkjob.cpp:957:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:964:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:970:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:985:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:1903:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2219:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2227:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2298:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2548:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2577:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2590:  [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.
upp/uppsrc/coff/uld/linkjob.cpp:2596:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2603:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2610:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2617:  [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.
upp/uppsrc/coff/uld/linkjob.cpp:2625:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2633:  [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.
upp/uppsrc/coff/uld/linkjob.cpp:2639:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2706:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:2737:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:3002:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:3048:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:3072:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:3096:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/uld/linkjob.cpp:3438:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/util.cpp:25:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/coff/util.cpp:206:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/coff/util.cpp: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. 
upp/uppsrc/ide/Builders/CppBuilder.cpp: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. 
upp/uppsrc/ide/Builders/GccBuilder.cpp:101:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/Builders/GccBuilder.cpp:103:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/Common/Common.cpp: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. 
upp/uppsrc/ide/Common/Common.cpp:373:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/Common/Common.cpp:380:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/Common/Common.cpp:383:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/Common/Common.h:322:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/Common/Workspace.cpp: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. 
upp/uppsrc/ide/Debuggers/Code.cpp:9:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/ide/Debuggers/Code.cpp: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. 
upp/uppsrc/ide/Debuggers/Debug.cpp: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. 
upp/uppsrc/ide/Debuggers/Gdb.cpp:235:  [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). 
upp/uppsrc/ide/Debuggers/Mem.cpp:20:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Debuggers/Pdb.cpp:98:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Debuggers/Pdb.cpp:102:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Debuggers/Pdb.h:46:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/ide/Debuggers/Sym.cpp: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. 
upp/uppsrc/ide/Goto.cpp:77:  [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). 
upp/uppsrc/ide/Host.cpp:190:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Host.cpp:200:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Host.cpp:229:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Host.cpp:242:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Host.cpp:247:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Host.cpp:253:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/Install.cpp: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. 
upp/uppsrc/ide/Install.cpp:97:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/ide/Methods.cpp:41:  [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). 
upp/uppsrc/ide/OutputMode.cpp:218:  [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). 
upp/uppsrc/ide/OutputMode.cpp:219:  [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). 
upp/uppsrc/ide/OutputMode.cpp:221:  [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). 
upp/uppsrc/ide/OutputMode.cpp:327:  [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). 
upp/uppsrc/ide/OutputMode.cpp:328:  [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). 
upp/uppsrc/ide/OutputMode.cpp:330:  [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). 
upp/uppsrc/ide/Uninstall.cpp: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. 
upp/uppsrc/ide/UppWspc.cpp:144:  [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?. 
upp/uppsrc/ide/UppWspc.cpp:145:  [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?. 
upp/uppsrc/ide/UppWspc.cpp:149:  [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?. 
upp/uppsrc/ide/UppWspc.cpp:343:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/ide/UppWspc.cpp:536:  [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?. 
upp/uppsrc/ide/idebar.cpp:34:  [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?. 
upp/uppsrc/ide/idefile.cpp:259:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/idefile.cpp:261:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/idefile.cpp:270:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/idefile.cpp:280:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/idefile.cpp:283:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/ide/idewin.cpp:726:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/ide/idewin.cpp:750:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp: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. 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp:96:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/astyle/ASEnhancer.cpp: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. 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp:101:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/plugin/astyle/astyle.h:76:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/astyle/astyle_main.cpp:190:  [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.
upp/uppsrc/plugin/astyle/astyle_main.cpp:381:  [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). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:392:  [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). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:407:  [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). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:422:  [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). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:433:  [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). 
upp/uppsrc/plugin/bmp/BmpWrite.cpp:83:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1021:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1043:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1049:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1222:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/plugin/bz2/lib/bzip2.c:1311:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1332:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1410:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/plugin/bz2/lib/bzip2.c:1497:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1509:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1639:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:383:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:457:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:512:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:516:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:521:  [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?. 
upp/uppsrc/plugin/bz2/lib/bzlib.c:1412:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/bz2/lib/bzlib.c:1415:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/bz2/lib/bzlib.c:1447:  [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?. 
upp/uppsrc/plugin/bz2/lib/dlltest.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. 
upp/uppsrc/plugin/bz2/lib/dlltest.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. 
upp/uppsrc/plugin/bz2/lib/dlltest.c:125:  [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?. 
upp/uppsrc/plugin/bz2/lib/dlltest.c:148:  [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?. 
upp/uppsrc/plugin/bz2/lib/spewG.c:21:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/bz2/lib/unzcrash.c:71:  [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?. 
upp/uppsrc/plugin/dbf/dbf.cpp:179:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/dbf/dbf.cpp:213:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/dbf/dbf.cpp: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. 
upp/uppsrc/plugin/dbf/dbf.cpp:289:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/dbf/dbf.cpp:658:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/dbf/dbf.cpp:782:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/ftp.cpp: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. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp: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. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp: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. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:157:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:227:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:310:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:313:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:327:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:382:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:387:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:448:  [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). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:458:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:461:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:466:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:472:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:491:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:501:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:508:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:595:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:608:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:614:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp: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. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:664:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:670:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:675:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:701:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:708:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:714:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:721:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:759:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:766:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:784:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:790:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:796:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:869:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:875:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:919:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:924:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:928:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:934:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:938:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:942:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:946:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:950:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1099:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp: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. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1156:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1185:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1233:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1238:  [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?. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1266:  [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.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1307:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1312:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1335:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1377:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1398:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.h:76:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ftp/lib/ftplib.h:76:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/gif/gifupp.cpp:115:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/gif/gifupp.cpp:240:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/gif/gifupp.cpp:726:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/gif/gifupp.cpp:728:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/gif/gifupp.cpp:1115:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/gif/gifupp.cpp:1330:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:358:  [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?. 
upp/uppsrc/plugin/jpg/lib/ansi2knr.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?. 
upp/uppsrc/plugin/jpg/lib/cjpeg.c:562:  [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?. 
upp/uppsrc/plugin/jpg/lib/cjpeg.c:573:  [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?. 
upp/uppsrc/plugin/jpg/lib/ckconfig.c:297:  [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?. 
upp/uppsrc/plugin/jpg/lib/djpeg.c:274:  [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?. 
upp/uppsrc/plugin/jpg/lib/djpeg.c:504:  [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?. 
upp/uppsrc/plugin/jpg/lib/djpeg.c:515:  [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?. 
upp/uppsrc/plugin/jpg/lib/example.c:114:  [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?. 
upp/uppsrc/plugin/jpg/lib/example.c:306:  [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?. 
upp/uppsrc/plugin/jpg/lib/jchuff.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. 
upp/uppsrc/plugin/jpg/lib/jchuff.h: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. 
upp/uppsrc/plugin/jpg/lib/jcmarker.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. 
upp/uppsrc/plugin/jpg/lib/jcmarker.c:229:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/jpg/lib/jdhuff.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. 
upp/uppsrc/plugin/jpg/lib/jerror.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. 
upp/uppsrc/plugin/jpg/lib/jinclude.h:62:  [2] (buffer) bcopy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/jpg/lib/jinclude.h:68:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/jpg/lib/jmemansi.c:144:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:151:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/jpg/lib/jmemdos.c:153:  [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?. 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:339:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:360:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/jpg/lib/jmemdos.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. 
upp/uppsrc/plugin/jpg/lib/jmemdos.c:393:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/jpg/lib/jmemdos.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. 
upp/uppsrc/plugin/jpg/lib/jmemname.c:103:  [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?. 
upp/uppsrc/plugin/jpg/lib/jmemname.c:251:  [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?. 
upp/uppsrc/plugin/jpg/lib/jmemsys.h: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. 
upp/uppsrc/plugin/jpg/lib/jmemsys.h: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. 
upp/uppsrc/plugin/jpg/lib/jmemsys.h: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. 
upp/uppsrc/plugin/jpg/lib/jpeglib.h:682:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/jpg/lib/jpegtran.c:409:  [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?. 
upp/uppsrc/plugin/jpg/lib/jpegtran.c:420:  [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?. 
upp/uppsrc/plugin/jpg/lib/rdjpgcom.c:471:  [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?. 
upp/uppsrc/plugin/jpg/lib/rdswitch.c:90:  [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?. 
upp/uppsrc/plugin/jpg/lib/rdswitch.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?. 
upp/uppsrc/plugin/jpg/lib/wrbmp.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. 
upp/uppsrc/plugin/jpg/lib/wrbmp.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. 
upp/uppsrc/plugin/jpg/lib/wrbmp.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. 
upp/uppsrc/plugin/jpg/lib/wrbmp.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. 
upp/uppsrc/plugin/jpg/lib/wrgif.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. 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:442:  [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?. 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:485:  [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?. 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:512:  [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?. 
upp/uppsrc/plugin/jpg/lib/wrrle.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. 
upp/uppsrc/plugin/jpg/lib/wrrle.c:202:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/jpg/lib/wrtarga.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. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:588:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:591:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:592:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:593:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:594:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:595:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:596:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:597:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:638:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:645:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:654:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:656:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:658:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:660:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:662:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:674:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:676:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:678:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:680:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:682:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:684:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:686:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:709:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:718:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:723:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:727:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:731:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/disasm.c:748:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:30:  [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?. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:323:  [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.
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:489:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:561:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:593:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:624:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:711:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ndisasm/lib/ndisasm.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. 
upp/uppsrc/plugin/ndisasm/lib/ndisasm.c:41:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/ndisasm/lib/ndisasm.c:205:  [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?. 
upp/uppsrc/plugin/ndisasm/lib/ndisasm.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. 
upp/uppsrc/plugin/ndisasm/ndisupp.cpp: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. 
upp/uppsrc/plugin/pcre/lib/dftables.c:87:  [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?. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:773:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:2786:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3405:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3430:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3523:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3672:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3697:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3727:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3914:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:3980:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:4549:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_dfa_exec.c:426:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_exec.c:1027:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_exec.c:1056:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_exec.c:1242:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_exec.c:4886:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_get.c:244:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_get.c:333:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_get.c:401:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_internal.h:243:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_internal.h:256:  [2] (buffer) bcopy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcre/lib/pcre_study.c:574:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/pcx/pcx.cpp:155:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/png/lib/example.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. 
upp/uppsrc/plugin/png/lib/example.c:63:  [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?. 
upp/uppsrc/plugin/png/lib/example.c:92:  [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?. 
upp/uppsrc/plugin/png/lib/example.c:567:  [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?. 
upp/uppsrc/plugin/png/lib/png.c:23:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/png.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. 
upp/uppsrc/plugin/png/lib/png.c:660:  [2] (buffer) wchar_t:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/png.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. 
upp/uppsrc/plugin/png/lib/pngconf.h:1467:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/png/lib/pngerror.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. 
upp/uppsrc/plugin/png/lib/pngerror.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. 
upp/uppsrc/plugin/png/lib/pngerror.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. 
upp/uppsrc/plugin/png/lib/pngerror.c:193:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngerror.c:218:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngerror.c:274:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngread.c:111:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngread.c:192:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngrtran.c:1265:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngrutil.c:32:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/png/lib/pngrutil.c:36:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/png/lib/pngrutil.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. 
upp/uppsrc/plugin/png/lib/pngrutil.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. 
upp/uppsrc/plugin/png/lib/pngtest.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. 
upp/uppsrc/plugin/png/lib/pngtest.c:622:  [2] (buffer) TCHAR:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngtest.c:624:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngtest.c:629:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/png/lib/pngtest.c:632:  [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?. 
upp/uppsrc/plugin/png/lib/pngtest.c:640:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/png/lib/pngtest.c:643:  [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?. 
upp/uppsrc/plugin/png/lib/pngtest.c:1214:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/png/lib/pngtest.c:1217:  [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?. 
upp/uppsrc/plugin/png/lib/pngtest.c:1225:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/png/lib/pngtest.c:1228:  [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?. 
upp/uppsrc/plugin/png/lib/pngwrite.c:504:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngwrite.c:575:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngwutil.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. 
upp/uppsrc/plugin/png/lib/pngwutil.c:1238:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngwutil.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. 
upp/uppsrc/plugin/png/lib/pngwutil.c:1604:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/lib/pngwutil.c:1613:  [2] (buffer) wchar_t:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/png/pngupp.cpp:455:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:232:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:232:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:232:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:240:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:240:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:240:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:240:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:240:  [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). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:240:  [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). 
upp/uppsrc/plugin/sqlite3/lib/alter.c:608:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/attach.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. 
upp/uppsrc/plugin/sqlite3/lib/attach.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. 
upp/uppsrc/plugin/sqlite3/lib/attach.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. 
upp/uppsrc/plugin/sqlite3/lib/attach.c:120:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/attach.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. 
upp/uppsrc/plugin/sqlite3/lib/attach.c:241:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/attach.c:245:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/bitvec.c:159:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/bitvec.c:190:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:701:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:710:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:762:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:853:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:1145:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:1782:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:2811:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:3033:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:3036:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:3964:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:3986:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:3988:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4006:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4008:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4060:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4367:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4529:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4560:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4624:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4954:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:4956:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5015:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5029:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5236:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5296:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5410:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5472:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5473:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5477:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:5641:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/btree.c:6440:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/build.c:239:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/build.c:251:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/build.c:255:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/build.c:460:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/build.c:2161:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/build.c:2189:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/build.c:2442:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/build.c:2516:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/callback.c:65:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/callback.c:174:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/callback.c:311:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/date.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. 
upp/uppsrc/plugin/sqlite3/lib/date.c:730:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/date.c:750:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/date.c:769:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/date.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. 
upp/uppsrc/plugin/sqlite3/lib/date.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. 
upp/uppsrc/plugin/sqlite3/lib/expr.c:312:  [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). 
upp/uppsrc/plugin/sqlite3/lib/expr.c:402:  [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). 
upp/uppsrc/plugin/sqlite3/lib/expr.c:495:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/expr.c:1192:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/expr.c:1837:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:485:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:494:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:495:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:771:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.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. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:956:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:988:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1016:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1055:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1717:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1752:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1755:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1928:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:2591:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:3363:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:3375:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/sqlite3/lib/fts3.c:3690:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4044:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4309:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4429:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4924:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4967:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4979:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4980:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:4991:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:5047:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:5070:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:5088:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:5100:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:5635:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:6201:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:6232:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3_hash.c:349:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3_icu.c:73:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3_porter.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. 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer.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. 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer.c:163:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer.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. 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer.c:260:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer1.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. 
upp/uppsrc/plugin/sqlite3/lib/func.c:226:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/func.c:269:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/func.c:289:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/func.c:853:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/func.c:859:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/func.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. 
upp/uppsrc/plugin/sqlite3/lib/func.c:1006:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/func.c:1012:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/func.c:1035:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/func.c:1104:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/func.c:1160:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/func.c:1567:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/hash.c:398:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/insert.c:1207:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/journal.c:100:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/journal.c:123:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/keywordhash.h:17:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/keywordhash.h:27:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/keywordhash.h: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. 
upp/uppsrc/plugin/sqlite3/lib/keywordhash.h: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. 
upp/uppsrc/plugin/sqlite3/lib/keywordhash.h:72:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/legacy.c:133:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/loadext.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. 
upp/uppsrc/plugin/sqlite3/lib/loadext.c:354:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/loadext.c:379:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/malloc.c:148:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/malloc.c:156:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/malloc.c:206:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem2.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. 
upp/uppsrc/plugin/sqlite3/lib/mem2.c:288:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem2.c:293:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem2.c:371:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem2.c:399:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem2.c:414:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/mem3.c:567:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem3.c:569:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem3.c:589:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/mem4.c:382:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem4.c:384:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem5.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. 
upp/uppsrc/plugin/sqlite3/lib/mem5.c:462:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/mem5.c:481:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/mutex_os2.c:110:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.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. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:747:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/sqlite3/lib/os_os2.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. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:843:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:850:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:857:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:867:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:871:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:875:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:879:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:883:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.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. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:1923:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2309:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2315:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2409:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2667:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2671:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2673:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:159:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:164:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:206:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:211:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1286:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1302:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1465:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1470:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1475:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1481:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:406:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/pager.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. 
upp/uppsrc/plugin/sqlite3/lib/pager.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. 
upp/uppsrc/plugin/sqlite3/lib/pager.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. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:978:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:988:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1063:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1128:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1158:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1509:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1519:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2152:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2153:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2225:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2230:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2231:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2999:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:3292:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:3446:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:4106:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:4174:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:4326:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:4721:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pager.c:4929:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:41:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:82:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:321:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:353:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:372:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:526:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:858:  [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). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:1118:  [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). 
upp/uppsrc/plugin/sqlite3/lib/prepare.c:75:  [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). 
upp/uppsrc/plugin/sqlite3/lib/prepare.c:108:  [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). 
upp/uppsrc/plugin/sqlite3/lib/prepare.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. 
upp/uppsrc/plugin/sqlite3/lib/printf.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. 
upp/uppsrc/plugin/sqlite3/lib/printf.c:749:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/printf.c:759:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/printf.c:774:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/printf.c:811:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/printf.c:841:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/printf.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. 
upp/uppsrc/plugin/sqlite3/lib/random.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. 
upp/uppsrc/plugin/sqlite3/lib/random.c:63:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/random.c:113:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/random.c:116:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/select.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. 
upp/uppsrc/plugin/sqlite3/lib/select.c:1099:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:144:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.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. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:316:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:319:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:324:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:750:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1012:  [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). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1036:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1072:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1144:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1168:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1234:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1292:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1323:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1399:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1423:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1436:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1443:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1456:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1580:  [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). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1593:  [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). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1699:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1712:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1723:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1734:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1818:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1855:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1905:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:2002:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/sqlite3ext.h:107:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/sqlite3ext.h:270:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/sqliteInt.h:701:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/table.c:96:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:318:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:472:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:476:  [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). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:491:  [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). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:523:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:547:  [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). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:618:  [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). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1043:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1080:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1192:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1245:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1314:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1392:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:2031:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:2073:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:2168:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:2572:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/utf.c:206:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/utf.c:313:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/utf.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. 
upp/uppsrc/plugin/sqlite3/lib/vdbe.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. 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:1031:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:1033:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:3248:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:548:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:558:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:626:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:633:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:636:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.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. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1683:  [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?. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1984:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:2004:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:2089:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbeblob.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. 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:106:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:522:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:552:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:572:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:595:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:650:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:34:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:791:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/where.c:240:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/where.c:527:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/where.c:1871:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/sqlite3/lib/where.c:2717:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/where.c:2720:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/where.c:2726:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/where.c:2729:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/sqlite3/lib/where.c:2734:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/mkg3states.c:407:  [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?. 
upp/uppsrc/plugin/tif/lib/mkspans.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. 
upp/uppsrc/plugin/tif/lib/mkspans.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. 
upp/uppsrc/plugin/tif/lib/mkversion.c:52:  [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?. 
upp/uppsrc/plugin/tif/lib/mkversion.c:67:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/mkversion.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. 
upp/uppsrc/plugin/tif/lib/mkversion.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. 
upp/uppsrc/plugin/tif/lib/mkversion.c:70:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/mkversion.c:141:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/mkversion.c:150:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:285:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:450:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:487:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_apple.c:221:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_atari.c:76:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_atari.c:215:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_dirinfo.c:841:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_dirread.c:1472:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_dirwrite.c:776:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_dirwrite.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. 
upp/uppsrc/plugin/tif/lib/tif_fax3.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. 
upp/uppsrc/plugin/tif/lib/tif_fax3.c:742:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_getimage.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. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:80:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.c:88:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.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. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:248:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.c:306:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.c:316:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.c:428:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.c:434:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/tif/lib/tif_getimage.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. 
upp/uppsrc/plugin/tif/lib/tif_getimage.c:2453:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_getimage.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. 
upp/uppsrc/plugin/tif/lib/tif_jpeg.c:225:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_jpeg.c:241:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_jpeg.c:915:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_msdos.c:109:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_msdos.c:151:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_ojpeg.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. 
upp/uppsrc/plugin/tif/lib/tif_ojpeg.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. 
upp/uppsrc/plugin/tif/lib/tif_print.c:76:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_print.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. 
upp/uppsrc/plugin/tif/lib/tif_swab.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. 
upp/uppsrc/plugin/tif/lib/tif_swab.c:176:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_unix.c:169:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_unix.c:171:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_unix.c:265:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_vms.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. 
upp/uppsrc/plugin/tif/lib/tif_vms.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. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:176:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:248:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:251:  [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?. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:286:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_vms.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. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:384:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_win3.c:171:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_win3.c:205:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_win3.c:218:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:301:  [2] (buffer) CopyMemory:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:306:  [2] (buffer) CopyMemory:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tif_win32.c:322:  [2] (buffer) CopyMemory:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/lib/tiffcomp.h:196:  [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?. 
upp/uppsrc/plugin/tif/tifupp.cpp:101:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/tifupp.cpp:113:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/tifupp.cpp:303:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/tifupp.cpp:502:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/tif/tifupp.cpp:713:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/tif/tifupp.cpp:768:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/plugin/tif/tifupp.cpp:771:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/plugin/tif/tifupp.cpp:776:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/plugin/tif/tifupp.cpp:793:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/plugin/tif/tifupp.cpp:800:  [2] (tmpfile) tmpfile:
  Function tmpfile() has a security flaw on some systems (e.g., older
  System V systems). 
upp/uppsrc/plugin/tif/tifupp.cpp:1024:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/plugin/z/lib/example.c:71:  [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.
upp/uppsrc/plugin/z/lib/example.c:119:  [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.
upp/uppsrc/plugin/z/lib/example.c:209:  [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.
upp/uppsrc/plugin/z/lib/example.c:305:  [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.
upp/uppsrc/plugin/z/lib/example.c:384:  [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.
upp/uppsrc/plugin/z/lib/example.c:465:  [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.
upp/uppsrc/plugin/z/lib/gzio.c:84:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/gzio.c:199:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/gzio.c:202:  [2] (buffer) sprintf:
  Does not check for buffer overflows. Use snprintf or vsnprintf. Risk
  is low because the source has a constant maximum length.
upp/uppsrc/plugin/z/lib/gzio.c:531:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/gzio.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. 
upp/uppsrc/plugin/z/lib/gzio.c:877:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant string.
upp/uppsrc/plugin/z/lib/minigzip.c:104:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/minigzip.c:172:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/minigzip.c:199:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/minigzip.c:206:  [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?. 
upp/uppsrc/plugin/z/lib/minigzip.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. 
upp/uppsrc/plugin/z/lib/minigzip.c:250:  [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?. 
upp/uppsrc/plugin/z/lib/minigzip.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. 
upp/uppsrc/plugin/z/lib/minigzip.c:278:  [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.
upp/uppsrc/plugin/z/lib/trees.c:333:  [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?. 
upp/uppsrc/plugin/z/lib/zutil.c:16:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/plugin/z/lib/zutil.h: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. 
upp/uppsrc/plugin/z/lib/zutil.h:102:  [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?. 
upp/uppsrc/plugin/z/lib/zutil.h:148:  [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?. 
upp/uppsrc/plugin/z/lib/zutil.h:179:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination. Make
  sure destination can always hold the source data. 
upp/uppsrc/umk/umk.cpp:21:  [2] (buffer) char:
  Statically-sized arrays can be overflowed. Perform bounds checking,
  use functions that limit length, or ensure that the size is larger than
  the maximum possible length. 
upp/uppsrc/umk/umk.cpp:24:  [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.
upp/uppsrc/umk/umk.cpp:26:  [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.
upp/bazaar/Rss/Rss.cpp:239:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/bazaar/Rss/Rss.cpp:246:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/bazaar/Signals/Signals.cpp:59:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/bazaar/SysExec/SysExec.cpp:17:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/bazaar/SysExec/SysExec.cpp:31:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/bazaar/SysExec/SysExec.cpp:256:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/bazaar/SysExec/SysExec.cpp:268:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/bazaar/UnitTest++/MemoryOutStream.cpp:64:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/bazaar/UnitTest++/MemoryOutStream.cpp:65:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/bazaar/UnitTest++/MemoryOutStream.cpp:133:  [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.
upp/bazaar/UnitTest++/Posix/TimeHelpersPosix.cpp:32:  [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. 
upp/benchmarks/AllocMT/Chris.cpp:935:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/CodeEditor/CodeEditor.cpp:717:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CodeEditor/CodeEditor.cpp:719:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CodeEditor/CodeEditor.cpp:719:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/BlockStream.cpp:439:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/CharSet.cpp:1349:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/CharSet.cpp:1379:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/CharSet.cpp:1689:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/CharSet.cpp:1700:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/CharSet.cpp:1711:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Debug.cpp:23:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Debug.cpp:39:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Debug.cpp:53:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/Core/Debug.cpp:245:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Debug.cpp:406:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Debug.cpp:415:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Debug.cpp:460:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/Core/Dli.cpp:86:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Dli.cpp:90:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Format.cpp:10:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Format.cpp:14:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/LocalProcess.cpp:93:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/LocalProcess.cpp:115:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/LocalProcess.cpp:199:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/LocalProcess.cpp:360:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/Log.cpp:16:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Log.cpp:76:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Log.cpp:91:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Log.cpp:151:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Log.cpp:154:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Log.cpp:158:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Log.cpp:161:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Path.cpp:97:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Random.cpp:164:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/Stream.cpp:859:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/Stream.cpp:860:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/Stream.cpp:861:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/Stream.cpp:1444:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Core/String.cpp:462:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/String.cpp:463:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/String.h:19:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/String.h:360:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/String.h:367:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/TimeDate.cpp:75:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/Core/TimeDate.cpp:89:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/Core/TimeDate.cpp:171:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/Core/Topic.cpp:35:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Util.cpp:31:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Util.cpp:159:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Util.cpp:443:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/WString.cpp:212:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/Win32Util.cpp:47:  [1] (buffer) wcslen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/parser.cpp:10:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Core/parser.cpp:442:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CtrlCore/Win32Clip.cpp:253:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CtrlCore/X11App.cpp:195:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CtrlLib/TrayIconX11.cpp:72:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CtrlLib/Win32.cpp:176:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/CtrlLib/Win32.cpp:182:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/DocTypes/QtfParser.cpp:118:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Draw/DrawText.cpp:343:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Draw/Image.cpp:458:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Draw/Image.cpp:460:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/OleDB/OleDB.cpp:83:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Oracle/Oci8.cpp:774:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Oracle/Oci8.cpp:875:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Oracle/Oci8.cpp:884:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Oracle/Oci8.cpp:885:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Oracle/OraCommon.cpp:71:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Oracle/contest.cpp:36:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/PdfDraw/TTFReader.cpp:92:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/PdfDraw/TTFReader.cpp:115:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/RichText/ParseQtf.cpp:325:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Sql/SqlCase.cpp:204:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/CalcNode.cpp:1098:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/CalcType.cpp:60:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/nls_bw.hpp:718:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/nls_bw.hpp:732:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/nls_bw.hpp:746:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/nls_bw.hpp:760:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/nls_bw.hpp:774:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/nls_bw.hpp:788:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/util.cpp:392:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/TCore/util.cpp:393:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/TServ/tserv.cpp:139:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/TServ/tserv.cpp:711:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/TServ/tserv.cpp:718:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/httpsrv.cpp:318:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/httpsrv.cpp:320:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/httpsrv.cpp:325:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/httpsrv.cpp:326:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/httpsrv.cpp:326:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/smtp.cpp:262:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/socket.cpp:483:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/socket.cpp:523:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:525:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:530:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:533:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:534:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:535:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:536:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:537:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:551:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:558:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:560:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:563:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:564:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:565:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:566:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.cpp:568:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.h:91:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/socket.h:92:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/sproc.cpp:158:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/sproc.cpp:178:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/sproc.cpp:266:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/sproc.cpp:422:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/Web/sproc.cpp:518:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/sproc.cpp:522:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/util.cpp:107:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/Web/wisapi/wisapi.cpp:215:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/binobj/binobj.cpp:352:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/coff/binobj/binobj.cpp:364:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/coff/binobj/binobj.cpp:415:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/uld/dump.cpp:14:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/uld/dump.cpp:59:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/uld/linkjob.cpp:820:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/uld/linkjob.cpp:883:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/uld/linkjob.cpp:3373:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/uld/linkjob.cpp:3426:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/coff/util.cpp:75:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/ide/Builders/MscBuilder.cpp:8:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/ide/Host.cpp:219:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/ide/Host.cpp:275:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/ide/Install.cpp:97:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/ide/idewin.cpp:645:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASBeautifier.cpp:696:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASBeautifier.cpp:712:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASBeautifier.cpp:725:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASBeautifier.cpp:731:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASBeautifier.cpp:734:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp:448:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/ASEnhancer.cpp:454:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/astyle.h:489:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:71:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:192:  [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.
upp/uppsrc/plugin/astyle/astyle_main.cpp:195:  [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.
upp/uppsrc/plugin/astyle/astyle_main.cpp:197:  [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.
upp/uppsrc/plugin/astyle/astyle_main.cpp:282:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/astyle/astyle_main.cpp:284:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:411:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:990:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:991:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1000:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1012:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1182:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1183:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1194:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1194:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1802:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1911:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2.c:1912:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:237:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:295:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:374:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzip2recover.c:377:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/bz2/lib/bzlib.c:929:  [1] (buffer) fgetc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/bz2/lib/bzlib.c:1440:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/plugin/dbf/dbf.cpp:753:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:89:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:320:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:602:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:612:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:630:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:631:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:861:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:893:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:955:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:957:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1101:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1141:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1158:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1187:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1241:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1310:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1338:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1344:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1379:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1380:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ftp/lib/ftplib.cpp:1400:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:260:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:374:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:397:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:485:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/ansi2knr.c:518:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/cjpeg.c:92:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/jerror.h:245:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/jpg/lib/jerror.h:301:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/jpg/lib/jmemmac.c:242:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/rdbmp.c:74:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdbmp.c:210:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:88:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:104:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:105:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:106:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:127:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:130:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:178:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:207:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:208:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:209:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdcolmap.c:240:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdjpgcom.c:64:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdppm.c:90:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdppm.c:93:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdppm.c:303:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdppm.c:306:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdswitch.c:27:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdswitch.c:30:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdtarga.c:94:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdtarga.c:130:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/rdtarga.c:161:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:78:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:458:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:465:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:469:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/jpg/lib/wrjpgcom.c:546:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/ndisasm/lib/disasm.c:740:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:95:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:126:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:695:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:756:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:757:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:1076:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:1095:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/ndisasm/lib/nasmlib.c:1096:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/pcre/lib/pcre_compile.c:5992:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/pcre/lib/pcre_dfa_exec.c:472:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/pcre/lib/pcre_internal.h:240:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/png/lib/pngconf.h:1464:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/png/lib/pngconf.h:1465:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/png/lib/pngrio.c:96:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngrio.c:103:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngrio.c:106:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngrio.c:108:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngrio.c:109:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngrio.c:113:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngrio.c:114:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngtest.c:336:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngtest.c:343:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngtest.c:344:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngtest.c:348:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngtest.c:349:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/png/lib/pngwutil.c:1616:  [1] (buffer) wcslen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/png/lib/pngwutil.c:1620:  [1] (buffer) wcslen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:231:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:239:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/alter.c:315:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/attach.c:340:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:278:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:342:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:369:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:385:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:531:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:562:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:566:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:629:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:631:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1260:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1350:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1371:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1376:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1381:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1383:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1590:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:1599:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2148:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2187:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2477:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2489:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2496:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2560:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/build.c:2633:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/callback.c:28:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/callback.c:59:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/callback.c:161:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/date.c:617:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/date.c:865:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/date.c:891:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/date.c:899:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/date.c:904:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:531:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1726:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1737:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:1738:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:2569:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:2769:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:2779:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:2909:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3.c:3829:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_hash.c:100:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_icu.c:63:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_icu.c:115:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_porter.c:104:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_porter.c:550:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer1.c:78:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/fts3_tokenizer1.c:128:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/func.c:1157:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/func.c:1468:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/func.c:1486:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/func.c:1515:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/hash.c:103:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/insert.c:1210:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/insert.c:1213:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/legacy.c:130:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/main.c:466:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/main.c:593:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/main.c:890:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/main.c:906:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/main.c:920:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/malloc.c:146:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/malloc.c:194:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/malloc.c:205:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/mem2.c:396:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:753:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:760:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_os2.c:818:  [1] (buffer) strncat:
  Easily used incorrectly (e.g., incorrectly computing the correct
  maximum size to add). Consider strlcat or automatically resizing strings. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:798:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2235:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2312:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2523:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2529:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2572:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2675:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/sqlite3/lib/os_unix.c:2694:  [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. 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1312:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/os_win.c:1316:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1133:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pager.c:1612:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2115:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2128:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pager.c:2226:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:43:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/pragma.c:1183:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/printf.c:496:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/printf.c:630:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/printf.c:724:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/select.c:196:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/select.c:210:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/select.c:1065:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/select.c:1093:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/select.c:1195:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:473:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:520:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:541:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:543:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:575:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:576:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:723:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:724:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:890:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1062:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1198:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1205:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1220:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1352:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1411:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1414:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1510:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1559:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1706:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1716:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1803:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1803:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1816:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:1845:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/shell.c:2063:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/table.c:93:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:385:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1337:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1338:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1358:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1378:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1423:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1437:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1578:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1823:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/tclsqlite.c:1976:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for
  invalid pointers. 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:117:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:254:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:260:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:463:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:487:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:552:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/trigger.c:644:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:345:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:347:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:350:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:359:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:362:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:382:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:394:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbe.c:820:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:573:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:620:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:624:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:807:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:840:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:862:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1213:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1286:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbeaux.c:1287:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:237:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vdbemem.c:883:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:30:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:237:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:285:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:296:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:401:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:786:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/vtab.c:791:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/where.c:2714:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/sqlite3/lib/where.c:2732:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:331:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/lib/tif_acorn.c:369:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/lib/tif_apple.c:152:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_compress.c:195:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_dir.c:59:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_dirwrite.c:588:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_extension.c:105:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_msdos.c:39:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/lib/tif_open.c:161:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_stream.cxx:62:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/lib/tif_unix.c:58:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:52:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/lib/tif_vms.c:136:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win3.c:207:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/plugin/tif/lib/tif_win3.c:208:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win3.c:209:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/plugin/tif/lib/tif_win3.c:220:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/plugin/tif/lib/tif_win3.c:221:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win3.c:222:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.
upp/uppsrc/plugin/tif/lib/tif_win32.c:346:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:347:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:347:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:350:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:374:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:375:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:375:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tif_win32.c:378:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/tif/lib/tiffcomp.h:199:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:377:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:378:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:464:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:485:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:536:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:538:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:541:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/tif/tifupp.cpp:556:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/example.c:66:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/example.c:94:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/example.c:146:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/example.c:170:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/example.c:345:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/example.c:444:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/gzio.c:105:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/gzio.c:542:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/gzio.c:566:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/gzio.c:596:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/gzio.c:875:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/gzio.c:875:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/z/lib/infblock.c:212:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infblock.c:212:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infblock.c:213:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infblock.c:346:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infblock.c:346:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infblock.c:347:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infblock.c:356:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infcodes.c:226:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infutil.c:34:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infutil.h:56:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infutil.h:78:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/infutil.h:80:  [1] (buffer) read:
  Check buffer boundaries if used in a loop. 
upp/uppsrc/plugin/z/lib/minigzip.c:232:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/plugin/zip/Zip.cpp:39:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated (it could cause a
  crash if unprotected). 
upp/uppsrc/umk/umk.cpp:29:  [1] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination.
  Consider using strncat or strlcat (warning, strncat is easily misused).
  Risk is low because the source is a constant character.

Hits = 2065
Lines analyzed = 594941 in 19.77 seconds (30879 lines/second)
Physical Source Lines of Code (SLOC) = 534353
Hits@level = [0]   0 [1] 496 [2] 1210 [3]  90 [4] 266 [5]   3
Hits@level+ = [0+] 2065 [1+] 2065 [2+] 1569 [3+] 359 [4+] 269 [5+]   3
Hits/KSLOC@level+ = [0+] 3.86449 [1+] 3.86449 [2+] 2.93626 [3+] 0.671841 [4+] 0.503413 [5+] 0.00561427
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
