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/libpog-0.5.3/deps/fmt/fmt/include/fmt/chrono.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/color.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/compile.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/core.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/locale.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/ostream.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/posix.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/ranges.h
Examining data/libpog-0.5.3/deps/fmt/fmt/include/fmt/safe-duration-cast.h
Examining data/libpog-0.5.3/deps/fmt/fmt/src/format.cc
Examining data/libpog-0.5.3/deps/fmt/fmt/src/posix.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/bitmap256.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/bitstate.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/compile.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/dfa.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/filtered_re2.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/filtered_re2.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/mimics_pcre.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/nfa.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/onepass.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/parse.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/perl_groups.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/pod_array.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/prefilter.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/prefilter.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/prefilter_tree.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/prefilter_tree.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/prog.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/prog.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/re2.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/re2.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/regexp.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/regexp.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/set.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/set.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/simplify.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/sparse_array.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/sparse_set.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/stringpiece.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/stringpiece.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/tostring.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/unicode_casefold.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/unicode_casefold.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/unicode_groups.cc
Examining data/libpog-0.5.3/deps/re2/re2/re2/unicode_groups.h
Examining data/libpog-0.5.3/deps/re2/re2/re2/walker-inl.h
Examining data/libpog-0.5.3/deps/re2/re2/util/benchmark.cc
Examining data/libpog-0.5.3/deps/re2/re2/util/benchmark.h
Examining data/libpog-0.5.3/deps/re2/re2/util/flags.h
Examining data/libpog-0.5.3/deps/re2/re2/util/fuzz.cc
Examining data/libpog-0.5.3/deps/re2/re2/util/logging.h
Examining data/libpog-0.5.3/deps/re2/re2/util/malloc_counter.h
Examining data/libpog-0.5.3/deps/re2/re2/util/mix.h
Examining data/libpog-0.5.3/deps/re2/re2/util/mutex.h
Examining data/libpog-0.5.3/deps/re2/re2/util/pcre.cc
Examining data/libpog-0.5.3/deps/re2/re2/util/pcre.h
Examining data/libpog-0.5.3/deps/re2/re2/util/rune.cc
Examining data/libpog-0.5.3/deps/re2/re2/util/strutil.cc
Examining data/libpog-0.5.3/deps/re2/re2/util/strutil.h
Examining data/libpog-0.5.3/deps/re2/re2/util/test.cc
Examining data/libpog-0.5.3/deps/re2/re2/util/test.h
Examining data/libpog-0.5.3/deps/re2/re2/util/utf.h
Examining data/libpog-0.5.3/deps/re2/re2/util/util.h
Examining data/libpog-0.5.3/examples/calculator/calculator.cpp
Examining data/libpog-0.5.3/examples/ini/ini.cpp
Examining data/libpog-0.5.3/include/pog/action.h
Examining data/libpog-0.5.3/include/pog/automaton.h
Examining data/libpog-0.5.3/include/pog/digraph_algo.h
Examining data/libpog-0.5.3/include/pog/errors.h
Examining data/libpog-0.5.3/include/pog/filter_view.h
Examining data/libpog-0.5.3/include/pog/grammar.h
Examining data/libpog-0.5.3/include/pog/html_report.h
Examining data/libpog-0.5.3/include/pog/item.h
Examining data/libpog-0.5.3/include/pog/operations/follow.h
Examining data/libpog-0.5.3/include/pog/operations/lookahead.h
Examining data/libpog-0.5.3/include/pog/operations/operation.h
Examining data/libpog-0.5.3/include/pog/operations/read.h
Examining data/libpog-0.5.3/include/pog/parser_report.h
Examining data/libpog-0.5.3/include/pog/parsing_table.h
Examining data/libpog-0.5.3/include/pog/pog.h
Examining data/libpog-0.5.3/include/pog/precedence.h
Examining data/libpog-0.5.3/include/pog/relations/includes.h
Examining data/libpog-0.5.3/include/pog/relations/lookback.h
Examining data/libpog-0.5.3/include/pog/relations/relation.h
Examining data/libpog-0.5.3/include/pog/rule.h
Examining data/libpog-0.5.3/include/pog/rule_builder.h
Examining data/libpog-0.5.3/include/pog/state.h
Parsing failed to find end of parameter list; semicolon terminated it in (lhs_kernel.begin(), lhs_kernel.end(), rhs_kernel.begin(), rhs_kernel.end(), [](const auto& left, const auto& right) {
return *left.get() == *right.get();
});
}
bool operator !=(const State& r
Examining data/libpog-0.5.3/include/pog/symbol.h
Examining data/libpog-0.5.3/include/pog/token.h
Examining data/libpog-0.5.3/include/pog/token_builder.h
Examining data/libpog-0.5.3/include/pog/types/state_and_rule.h
Examining data/libpog-0.5.3/include/pog/types/state_and_symbol.h
Examining data/libpog-0.5.3/include/pog/utils.h
Examining data/libpog-0.5.3/include/pog/parser.h
Examining data/libpog-0.5.3/include/pog/tokenizer.h
Examining data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc
Examining data/libpog-0.5.3/tests/googletest/gmock/gmock.h
Examining data/libpog-0.5.3/tests/googletest/gtest/gtest.h
Examining data/libpog-0.5.3/tests/pog_tests.cpp
Examining data/libpog-0.5.3/tests/test_automaton.cpp
Parsing failed to find end of parameter list; semicolon terminated it in (r->get_rhs().begin(), r->get_rhs().end(), rhs_syms.begin(), rhs_syms.end(), [](const auto* sym1, const auto* sym2) {
return sym1->get_index() == sym2->get_index();
});
if (r->get_lhs() == l
Examining data/libpog-0.5.3/tests/test_filter_view.cpp
Examining data/libpog-0.5.3/tests/test_grammar.cpp
Examining data/libpog-0.5.3/tests/test_item.cpp
Examining data/libpog-0.5.3/tests/test_parser.cpp
Examining data/libpog-0.5.3/tests/test_parsing_table.cpp
Examining data/libpog-0.5.3/tests/test_precedence.cpp
Examining data/libpog-0.5.3/tests/test_rule.cpp
Examining data/libpog-0.5.3/tests/test_rule_builder.cpp
Examining data/libpog-0.5.3/tests/test_state.cpp
Examining data/libpog-0.5.3/tests/test_symbol.cpp
Examining data/libpog-0.5.3/tests/test_token.cpp
Examining data/libpog-0.5.3/tests/test_token_builder.cpp
Examining data/libpog-0.5.3/tests/test_tokenizer.cpp
Examining data/libpog-0.5.3/tests/test_utils.cpp
FINAL RESULTS:
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h:70:24: [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.
# define FMT_SNPRINTF snprintf
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:179:6: [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.
void printf(buffer<Char>& buf, basic_string_view<Char> format,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:185:41: [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.
internal::truncating_iterator<OutputIt> printf(
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:192:17: [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.
using internal::printf; // For printing into memory_buffer.
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:602:32: [4] (format) vsprintf:
Potential format string problem (CWE-134). Make format string constant.
inline std::basic_string<Char> vsprintf(
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:605:3: [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.
printf(buffer, to_string_view(format), args);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:620:32: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
inline std::basic_string<Char> sprintf(const S& format, const Args&... args) {
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:622:10: [4] (format) vsprintf:
Potential format string problem (CWE-134). Make format string constant.
return vsprintf(to_string_view(format), {make_format_args<context>(args...)});
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:626:12: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
inline int vfprintf(std::FILE* f, const S& format,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:629:3: [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.
printf(buffer, to_string_view(format), args);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:647:12: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
inline int fprintf(std::FILE* f, const S& format, const Args&... args) {
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:649:10: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return vfprintf(f, to_string_view(format),
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:654:12: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
inline int vprintf(const S& format,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:656:10: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return vfprintf(stdout, to_string_view(format), args);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:670:12: [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.
inline int printf(const S& format_str, const Args&... args) {
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:672:10: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return vprintf(to_string_view(format_str),
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:677:12: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
inline int vfprintf(std::basic_ostream<Char>& os, const S& format,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:680:3: [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.
printf(buffer, to_string_view(format), args);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:689:33: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
typename ArgFormatter::iterator vprintf(internal::buffer<Char>& out,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:707:12: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
inline int fprintf(std::basic_ostream<Char>& os, const S& format_str,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/printf.h:710:10: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return vfprintf(os, to_string_view(format_str),
data/libpog-0.5.3/deps/re2/re2/util/benchmark.cc:16:9: [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.
#define snprintf _snprintf
data/libpog-0.5.3/deps/re2/re2/util/benchmark.cc:16:18: [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.
#define snprintf _snprintf
data/libpog-0.5.3/deps/re2/re2/util/strutil.cc:11:9: [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.
#define snprintf _snprintf
data/libpog-0.5.3/deps/re2/re2/util/strutil.cc:11:18: [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.
#define snprintf _snprintf
data/libpog-0.5.3/deps/re2/re2/util/strutil.cc:12:9: [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 (CWE-134). Use
a constant for the format specification.
#define vsnprintf _vsnprintf
data/libpog-0.5.3/deps/re2/re2/util/strutil.cc:104:16: [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 (CWE-134). Use
a constant for the format specification.
int result = vsnprintf(space, sizeof(space), format, backup_ap);
data/libpog-0.5.3/deps/re2/re2/util/strutil.cc:127:14: [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 (CWE-134). Use
a constant for the format specification.
result = vsnprintf(buf, length, format, backup_ap);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:1368:10: [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 (CWE-134). Use
a constant for the format specification.
# define vsnprintf _vsnprintf
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:4293:5: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vprintf(fmt, args);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:4314:3: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vprintf(fmt, args);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:4321:3: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vprintf(fmt, args);
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2321:20: [4] (buffer) StrNCpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
inline const char* StrNCpy(char* dest, const char* src, size_t n) {
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2391:26: [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.
# define GTEST_SNPRINTF_ _snprintf
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2393:26: [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.
# define GTEST_SNPRINTF_ snprintf
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:9806:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(\
data/libpog-0.5.3/deps/re2/re2/util/fuzz.cc:16:17: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
data[j] = random() & 0xFF;
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:465:37: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
void ShuffleRange(internal::Random* random, int begin, int end,
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:489:39: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
inline void Shuffle(internal::Random* random, std::vector<E>* v) {
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:490:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ShuffleRange(random, 0, static_cast<int>(v->size()), v);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:971:21: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
internal::Random* random() { return &random_; }
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:4090:48: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
void TestSuite::ShuffleTests(internal::Random* random) {
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:4091:11: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
Shuffle(random, &test_indices_);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:6499:7: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
random()->Reseed(static_cast<UInt32>(random_seed_));
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:6858:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ShuffleRange(random(), 0, last_death_test_suite_ + 1, &test_suite_indices_);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:6861:16: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
ShuffleRange(random(), last_death_test_suite_ + 1,
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:6866:30: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
test_suite->ShuffleTests(random());
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:9829:5: [3] (misc) InitializeCriticalSection:
Exceptions can be thrown in low-memory situations. Use
InitializeCriticalSectionAndSpinCount instead.
::InitializeCriticalSection(critical_section_);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:9844:5: [3] (misc) EnterCriticalSection:
On some versions of Windows, exceptions can be thrown in low-memory
situations. Use InitializeCriticalSectionAndSpinCount instead.
::EnterCriticalSection(critical_section_);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:9917:11: [3] (misc) InitializeCriticalSection:
Exceptions can be thrown in low-memory situations. Use
InitializeCriticalSectionAndSpinCount instead.
::InitializeCriticalSection(critical_section_);
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2360:27: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* const env = getenv(name);
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2363:10: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
return getenv(name);
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:13450:39: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
void ShuffleTests(internal::Random* random);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/core.h:836: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(val.data, &arg, sizeof(arg));
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/core.h:1242:11: [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.
mutable char data[sizeof(basic_format_arg<buffer_context<Char>>)];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/core.h:1248: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(&arg, data, sizeof(basic_format_arg<Context>));
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h:763: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 format[max_format_size];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h:848:16: [2] (buffer) MultiByteToWideChar:
Requires maximum length in CHARACTERS, not bytes (CWE-120).
int length = MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, s.data(),
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h:852:12: [2] (buffer) MultiByteToWideChar:
Requires maximum length in CHARACTERS, not bytes (CWE-120).
length = MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, s.data(), s_size,
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:201: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.
unsigned char value[sizeof(void*)];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:664:16: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char reset_color[5];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:665:16: [2] (buffer) wchar_t:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const wchar_t wreset_color[5];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:741: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(buffer_ + N, data::digits + index * 2, 2);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:884: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[std::numeric_limits<UInt>::digits / BASE_BITS + 1];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:1352: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 prefix[4];
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format.h:2882:11: [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.
mutable char buffer_[buffer_size];
data/libpog-0.5.3/deps/fmt/fmt/src/posix.cc:75:35: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FMT_RETRY_VAL(file_, FMT_SYSTEM(fopen(filename.c_str(), mode.c_str())),
data/libpog-0.5.3/deps/fmt/fmt/src/posix.cc:103:33: [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).
FMT_RETRY(fd_, FMT_POSIX_CALL(open(path.c_str(), oflag, mode)));
data/libpog-0.5.3/deps/re2/re2/re2/parse.cc:2186:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[UTFmax];
data/libpog-0.5.3/deps/re2/re2/re2/prefilter.cc:392:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[UTFmax];
data/libpog-0.5.3/deps/re2/re2/re2/re2.cc:1055:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/re2/re2.cc:1072:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/re2/re2.cc:1143:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/re2/re2.cc:1160:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/re2/re2.cc:1181:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxLength+1];
data/libpog-0.5.3/deps/re2/re2/re2/regexp.cc:341: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 tmp[sizeof *this];
data/libpog-0.5.3/deps/re2/re2/re2/regexp.cc:709:9: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[UTFmax];
data/libpog-0.5.3/deps/re2/re2/re2/stringpiece.cc:18:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buf, data_ + pos, ret);
data/libpog-0.5.3/deps/re2/re2/util/benchmark.cc:93: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 mb[100];
data/libpog-0.5.3/deps/re2/re2/util/benchmark.cc:94: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 suf[100];
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:829:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buf, str, n);
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:843:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:860:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:931:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:948:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxNumberLength+1];
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:969:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[kMaxLength];
data/libpog-0.5.3/deps/re2/re2/util/pcre.cc:971:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buf, str, n);
data/libpog-0.5.3/deps/re2/re2/util/rune.cc:186:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str[10];
data/libpog-0.5.3/deps/re2/re2/util/strutil.cc:97:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char space[1024];
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:2131:7: [2] (buffer) MultiByteToWideChar:
Requires maximum length in CHARACTERS, not bytes (CWE-120).
MultiByteToWideChar(CP_ACP, 0, ansi, length, nullptr, 0);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:2133:3: [2] (buffer) MultiByteToWideChar:
Requires maximum length in CHARACTERS, not bytes (CWE-120).
MultiByteToWideChar(CP_ACP, 0, ansi, length,
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:2934: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 error_text[kBufSize] = { '\0' };
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:3018: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 str[5]; // Big enough for the largest valid code point.
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:5669: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 tmp[1024];
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:5675: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 line[1024];
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:7716: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[256];
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:8139: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 executable_path[_MAX_PATH + 1]; // NOLINT
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:8688: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).
const int cwd_fd = open(".", O_RDONLY);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:9118: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 cwd[GTEST_PATH_MAX_ + 1] = { '\0' };
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:9121: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 cwd[GTEST_PATH_MAX_ + 1] = { '\0' };
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:9706: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).
const int fd = open("/proc/self/as", O_RDONLY);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10487:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buffer, regex, len);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10561: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 temp_dir_path[MAX_PATH + 1] = { '\0' }; // NOLINT
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10562: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 temp_file_path[MAX_PATH + 1] = { '\0' }; // NOLINT
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10599:29: [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).
const int captured_fd = mkstemp(name_template);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10949: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 text[5] = "";
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2333:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
return fopen(path, mode);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/chrono.h:602:57: [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).
facet.put(os, os, ' ', &time, format, format + std::strlen(format));
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/color.h:415:26: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return buffer + std::strlen(buffer);
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h:115:33: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (message == buffer_ && strlen(buffer_) == buffer_size_ - 1)
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/format-inl.h:129:29: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return result == 0 && strlen(buffer_) == buffer_size_ - 1 ? ERANGE
data/libpog-0.5.3/deps/fmt/fmt/include/fmt/posix.h:235:23: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
FMT_API std::size_t read(void* buffer, std::size_t count);
data/libpog-0.5.3/deps/fmt/fmt/src/posix.cc:151:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::size_t file::read(void* buffer, std::size_t count) {
data/libpog-0.5.3/deps/fmt/fmt/src/posix.cc:153:36: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
FMT_RETRY(result, FMT_POSIX_CALL(read(fd_, buffer, convert_rwcount(count))));
data/libpog-0.5.3/deps/re2/re2/re2/stringpiece.h:67:45: [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).
: data_(str), size_(str == NULL ? 0 : strlen(str)) {}
data/libpog-0.5.3/deps/re2/re2/re2/stringpiece.h:98:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size_ = str == NULL ? 0 : strlen(str);
data/libpog-0.5.3/include/pog/tokenizer.h:118:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
stream.read(block.data(), block.size());
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:2129: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).
const int length = strlen(ansi);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:3082:34: [1] (buffer) wcslen:
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).
num_chars = static_cast<int>(wcslen(str));
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:4965:32: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
segment = next_segment + strlen("]]>");
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:5573:18: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
result.reserve(strlen(str) + 1);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:6919:29: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
const size_t prefix_len = strlen(prefix);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:7344:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
else if (temp_dir[strlen(temp_dir) - 1] == '\\')
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:8302:38: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
status_zx = stderr_socket_.read(
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10225:33: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
const size_t full_regex_len = strlen(regex) + 10;
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:10475: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).
const size_t len = strlen(regex);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:11220:29: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
PrintCharsAsStringTo(s, strlen(s), os);
data/libpog-0.5.3/tests/googletest/gmock-gtest-all.cc:11237:29: [1] (buffer) wcslen:
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).
PrintCharsAsStringTo(s, wcslen(s), os);
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2322:10: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
return strncpy(dest, src, n);
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:2344:27: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return static_cast<int>(read(fd, buf, count));
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:3220:20: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (s.compare(0, strlen(prefix), prefix) == 0) {
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:3221:47: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
std::string::size_type end = s.find("::", strlen(prefix));
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:3224:15: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
s.erase(strlen("std"), end - strlen("std"));
data/libpog-0.5.3/tests/googletest/gtest/gtest.h:3224:36: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
s.erase(strlen("std"), end - strlen("std"));
ANALYSIS SUMMARY:
Hits = 134
Lines analyzed = 85727 in approximately 2.03 seconds (42177 lines/second)
Physical Source Lines of Code (SLOC) = 57955
Hits@level = [0] 91 [1] 27 [2] 54 [3] 17 [4] 36 [5] 0
Hits@level+ = [0+] 225 [1+] 134 [2+] 107 [3+] 53 [4+] 36 [5+] 0
Hits/KSLOC@level+ = [0+] 3.88232 [1+] 2.31214 [2+] 1.84626 [3+] 0.914503 [4+] 0.621172 [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.