Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/ticcutils-0.24/src/LogStream.cxx
Examining data/ticcutils-0.24/src/StringOps.cxx
Examining data/ticcutils-0.24/src/TreeHash.cxx
Examining data/ticcutils-0.24/src/Configuration.cxx
Examining data/ticcutils-0.24/src/Timer.cxx
Examining data/ticcutils-0.24/src/XMLtools.cxx
Examining data/ticcutils-0.24/src/zipper.cxx
Examining data/ticcutils-0.24/src/Tar.cxx
Examining data/ticcutils-0.24/src/FileUtils.cxx
Examining data/ticcutils-0.24/src/CommandLine.cxx
Examining data/ticcutils-0.24/src/SocketBasics.cxx
Examining data/ticcutils-0.24/src/ServerBase.cxx
Examining data/ticcutils-0.24/src/FdStream.cxx
Examining data/ticcutils-0.24/src/Unicode.cxx
Examining data/ticcutils-0.24/src/runtest.cxx
Examining data/ticcutils-0.24/src/testlogstream.cxx
Examining data/ticcutils-0.24/include/ticcutils/LogBuffer.h
Examining data/ticcutils-0.24/include/ticcutils/LogStream.h
Examining data/ticcutils-0.24/include/ticcutils/PrettyPrint.h
Examining data/ticcutils-0.24/include/ticcutils/XMLtools.h
Examining data/ticcutils-0.24/include/ticcutils/StringOps.h
Examining data/ticcutils-0.24/include/ticcutils/UnitTest.h
Examining data/ticcutils-0.24/include/ticcutils/Trie.h
Examining data/ticcutils-0.24/include/ticcutils/TreeHash.h
Examining data/ticcutils-0.24/include/ticcutils/Configuration.h
Examining data/ticcutils-0.24/include/ticcutils/Timer.h
Examining data/ticcutils-0.24/include/ticcutils/bz2stream.h
Examining data/ticcutils-0.24/include/ticcutils/gzstream.h
Examining data/ticcutils-0.24/include/ticcutils/zipper.h
Examining data/ticcutils-0.24/include/ticcutils/Tar.h
Examining data/ticcutils-0.24/include/ticcutils/Version.h
Examining data/ticcutils-0.24/include/ticcutils/FileUtils.h
Examining data/ticcutils-0.24/include/ticcutils/CommandLine.h
Examining data/ticcutils-0.24/include/ticcutils/SocketBasics.h
Examining data/ticcutils-0.24/include/ticcutils/ServerBase.h
Examining data/ticcutils-0.24/include/ticcutils/FdStream.h
Examining data/ticcutils-0.24/include/ticcutils/Unicode.h
Examining data/ticcutils-0.24/include/ticcutils/json.hpp
FINAL RESULTS:
data/ticcutils-0.24/include/ticcutils/json.hpp:1053:86: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define JSON_HEDLEY_PRINTF_FORMAT(string_idx,first_to_check) __declspec(vaformat(printf,string_idx,first_to_check))
data/ticcutils-0.24/include/ticcutils/json.hpp:5413:23: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(cr.data(), cr.size(), "%.2hhX", static_cast<unsigned char>(element_type));
data/ticcutils-0.24/include/ticcutils/json.hpp:7065:15: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(cr.data(), cr.size(), "%.2hhX", static_cast<unsigned char>(current));
data/ticcutils-0.24/include/ticcutils/json.hpp:8498:23: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(cs.data(), cs.size(), "<U+%.4X>", static_cast<unsigned char>(c));
data/ticcutils-0.24/include/ticcutils/json.hpp:14124:43: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(string_buffer.data() + bytes, 7, "\\u%04x",
data/ticcutils-0.24/include/ticcutils/json.hpp:14130:43: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(string_buffer.data() + bytes, 13, "\\u%04x\\u%04x",
data/ticcutils-0.24/include/ticcutils/json.hpp:14168:35: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(&sn[0], sn.size(), "%.2X", byte);
data/ticcutils-0.24/include/ticcutils/json.hpp:14262:27: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
(std::snprintf)(&sn[0], sn.size(), "%.2X", static_cast<std::uint8_t>(s.back()));
data/ticcutils-0.24/include/ticcutils/json.hpp:14463:36: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
std::ptrdiff_t len = (std::snprintf)(number_buffer.data(), number_buffer.size(), "%.*g", d, x);
data/ticcutils-0.24/src/runtest.cxx:618:16: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
assertEqual( system( cmd.c_str() ), 0 );
data/ticcutils-0.24/src/runtest.cxx:623:16: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
assertEqual( system( cmd.c_str() ), 0 );
data/ticcutils-0.24/src/runtest.cxx:633:16: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
assertEqual( system(cmd.c_str()), 0 );
data/ticcutils-0.24/src/runtest.cxx:636:16: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
assertEqual( system(cmd.c_str()), 0 );
data/ticcutils-0.24/src/runtest.cxx:641:16: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
assertEqual( system( cmd.c_str() ), 0 );
data/ticcutils-0.24/src/runtest.cxx:798:16: [4] (shell) system:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
assertEqual( system( cmd.c_str() ), 0 );
data/ticcutils-0.24/include/ticcutils/StringOps.h:133:15: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
std::string realpath( const std::string& );
data/ticcutils-0.24/src/StringOps.cxx:362:10: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
string realpath( const string& path ){
data/ticcutils-0.24/src/StringOps.cxx:370:19: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
char *res = ::realpath( in, out );
data/ticcutils-0.24/src/runtest.cxx:608:16: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
assertEqual( realpath( "" ), "" );
data/ticcutils-0.24/include/ticcutils/FdStream.h:59:8: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
bool open( int fd );
data/ticcutils-0.24/include/ticcutils/FdStream.h:73:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[bufferSize];
data/ticcutils-0.24/include/ticcutils/FdStream.h:90:8: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
bool open( int fd );
data/ticcutils-0.24/include/ticcutils/LogBuffer.h:100:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char time_line[50];
data/ticcutils-0.24/include/ticcutils/LogBuffer.h:107:3: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf( time_line+strlen(time_line), ":%03ld:", millitm() );
data/ticcutils-0.24/include/ticcutils/Tar.h:41:10: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
bool open( const std::string& );
data/ticcutils-0.24/include/ticcutils/bz2stream.h:235:12: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(pptr(), p + done, block_size);
data/ticcutils-0.24/include/ticcutils/bz2stream.h:428:10: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(putback_end - new_putback_num,
data/ticcutils-0.24/include/ticcutils/gzstream.h:52:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[bufferSize]; // data buffer
data/ticcutils-0.24/include/ticcutils/gzstream.h:66:18: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
gzstreambuf* open( const std::string &name, int open_mode );
data/ticcutils-0.24/include/ticcutils/gzstream.h:83:10: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
void open( const std::string&, int );
data/ticcutils-0.24/include/ticcutils/gzstream.h:99:10: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
void open( const std::string& name, int open_mode = std::ios::in ) {
data/ticcutils-0.24/include/ticcutils/gzstream.h:100:21: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
gzstreambase::open( name, open_mode);
data/ticcutils-0.24/include/ticcutils/gzstream.h:115:10: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
void open( const std::string& name, int open_mode = std::ios::out ) {
data/ticcutils-0.24/include/ticcutils/gzstream.h:116:21: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
gzstreambase::open( name, open_mode );
data/ticcutils-0.24/include/ticcutils/gzstream.h:120:29: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
gzstreambuf* gzstreambuf::open( const std::string& name, int open_mode) {
data/ticcutils-0.24/include/ticcutils/gzstream.h:162:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy( buffer + (4 - n_putback), gptr() - n_putback, n_putback);
data/ticcutils-0.24/include/ticcutils/gzstream.h:216:5: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
open( name, mode );
data/ticcutils-0.24/include/ticcutils/gzstream.h:223:22: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
void gzstreambase::open( const std::string& name, int open_mode ) {
data/ticcutils-0.24/include/ticcutils/gzstream.h:224:16: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if ( ! buf.open( name, open_mode ) )
data/ticcutils-0.24/include/ticcutils/json.hpp:1441:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
((struct { char v[sizeof(void) * 2]; } *) 1) \
data/ticcutils-0.24/include/ticcutils/json.hpp:7007:14: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(&result, vec.data(), sizeof(NumberType));
data/ticcutils-0.24/include/ticcutils/json.hpp:12566:14: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(vec.data(), &n, sizeof(NumberType));
data/ticcutils-0.24/include/ticcutils/json.hpp:12597:14: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(&result, &x, sizeof(x));
data/ticcutils-0.24/include/ticcutils/json.hpp:12695:10: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
std::memcpy(&target, &source, sizeof(Source));
data/ticcutils-0.24/src/FdStream.cxx:255:17: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
bool fdistream::open( int fd ){
data/ticcutils-0.24/src/FdStream.cxx:261:17: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
bool fdostream::open( int fd ){
data/ticcutils-0.24/src/FileUtils.cxx:327:21: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
int temp_file = mkstemp(filename);
data/ticcutils-0.24/src/LogStream.cxx:162:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char m[32];
data/ticcutils-0.24/src/LogStream.cxx:163:5: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf( m, "-%d", i );
data/ticcutils-0.24/src/ServerBase.cxx:66:9: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
_is.open(_id);
data/ticcutils-0.24/src/ServerBase.cxx:67:9: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
_os.open(_id);
data/ticcutils-0.24/src/ServerBase.cxx:322:14: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
(void) open ("/dev/null", O_RDWR);
data/ticcutils-0.24/src/SocketBasics.cxx:143:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[5];
data/ticcutils-0.24/src/SocketBasics.cxx:476:7: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char host_name[NI_MAXHOST];
data/ticcutils-0.24/src/Tar.cxx:53:13: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
bool tar::open( const string& name ){
data/ticcutils-0.24/src/Tar.cxx:201:53: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
int res = tar_extract_regfile( local_tar, (char*)tmpfile.c_str() );
data/ticcutils-0.24/src/Tar.cxx:206:11: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
result.open( tmpfile );
data/ticcutils-0.24/src/Tar.cxx:206:17: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
result.open( tmpfile );
data/ticcutils-0.24/src/Tar.cxx:212:33: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
cerr << "problem with " << tmpfile << endl;
data/ticcutils-0.24/src/Tar.cxx:260:47: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
stat = tar_extract_regfile( tar_file, (char*)tmpfile.c_str() );
data/ticcutils-0.24/src/Tar.cxx:265:9: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
result.open( tmpfile );
data/ticcutils-0.24/src/Tar.cxx:265:15: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
result.open( tmpfile );
data/ticcutils-0.24/src/Tar.cxx:271:31: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
cerr << "problem with " << tmpfile << endl;
data/ticcutils-0.24/src/Timer.cxx:52:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[256];
data/ticcutils-0.24/src/runtest.cxx:646:24: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
assertNoThrow( mytar.open( path + "test.tar" ) );
data/ticcutils-0.24/include/ticcutils/LogBuffer.h:107:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
sprintf( time_line+strlen(time_line), ":%03ld:", millitm() );
data/ticcutils-0.24/include/ticcutils/SocketBasics.h:73:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool read( std::string& );
data/ticcutils-0.24/include/ticcutils/SocketBasics.h:74:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool read( std::string&, unsigned int );
data/ticcutils-0.24/include/ticcutils/json.hpp:3935:21: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return std::fgetc(m_file);
data/ticcutils-0.24/include/ticcutils/json.hpp:4242:30: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
std::strlen(reinterpret_cast<const char*>(b))) {}
data/ticcutils-0.24/src/FdStream.cxx:150:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int num = read( fd, buffer+putbackSize, bufferSize - putbackSize );
data/ticcutils-0.24/src/SocketBasics.cxx:71:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool Socket::read( string& line ) {
data/ticcutils-0.24/src/SocketBasics.cxx:97:22: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bytes_read = ::read( sock, &last_read, 1 );
data/ticcutils-0.24/src/SocketBasics.cxx:128:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool Socket::read( string& result, unsigned int timeout ) {
data/ticcutils-0.24/src/SocketBasics.cxx:146:18: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ssize_t res = ::read( sock, buf, 1 );
ANALYSIS SUMMARY:
Hits = 75
Lines analyzed = 33492 in approximately 0.79 seconds (42271 lines/second)
Physical Source Lines of Code (SLOC) = 19967
Hits@level = [0] 0 [1] 10 [2] 46 [3] 4 [4] 15 [5] 0
Hits@level+ = [0+] 75 [1+] 75 [2+] 65 [3+] 19 [4+] 15 [5+] 0
Hits/KSLOC@level+ = [0+] 3.7562 [1+] 3.7562 [2+] 3.25537 [3+] 0.95157 [4+] 0.75124 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.