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/odb-2.4.0/odb/odb.cxx
Examining data/odb-2.4.0/odb/options.cxx
Examining data/odb-2.4.0/odb/profile.cxx
Examining data/odb-2.4.0/odb/option-functions.cxx
Examining data/odb-2.4.0/odb/option-types.cxx
Examining data/odb-2.4.0/odb/pragma.cxx
Examining data/odb-2.4.0/odb/source.cxx
Examining data/odb-2.4.0/odb/inline.cxx
Examining data/odb-2.4.0/odb/header.cxx
Examining data/odb-2.4.0/odb/instance.cxx
Examining data/odb-2.4.0/odb/lookup.cxx
Examining data/odb-2.4.0/odb/emitter.cxx
Examining data/odb-2.4.0/odb/diagnostics.cxx
Examining data/odb-2.4.0/odb/location.cxx
Examining data/odb-2.4.0/odb/common-query.cxx
Examining data/odb-2.4.0/odb/common.cxx
Examining data/odb-2.4.0/odb/sql-lexer.cxx
Examining data/odb-2.4.0/odb/sql-token.cxx
Examining data/odb-2.4.0/odb/traversal/union-template.cxx
Examining data/odb-2.4.0/odb/traversal/template.cxx
Examining data/odb-2.4.0/odb/traversal/enum.cxx
Examining data/odb-2.4.0/odb/traversal/elements.cxx
Examining data/odb-2.4.0/odb/traversal/derived.cxx
Examining data/odb-2.4.0/odb/traversal/class-template.cxx
Examining data/odb-2.4.0/odb/traversal/class.cxx
Examining data/odb-2.4.0/odb/traversal/relational/key.cxx
Examining data/odb-2.4.0/odb/traversal/relational/changelog.cxx
Examining data/odb-2.4.0/odb/semantics/unit.cxx
Examining data/odb-2.4.0/odb/semantics/union-template.cxx
Examining data/odb-2.4.0/odb/semantics/union.cxx
Examining data/odb-2.4.0/odb/semantics/template.cxx
Examining data/odb-2.4.0/odb/semantics/namespace.cxx
Examining data/odb-2.4.0/odb/semantics/fundamental.cxx
Examining data/odb-2.4.0/odb/semantics/enum.cxx
Examining data/odb-2.4.0/odb/semantics/derived.cxx
Examining data/odb-2.4.0/odb/semantics/class-template.cxx
Examining data/odb-2.4.0/odb/semantics/class.cxx
Examining data/odb-2.4.0/odb/semantics/relational/deferrable.cxx
Examining data/odb-2.4.0/odb/semantics/relational/name.cxx
Examining data/odb-2.4.0/odb/semantics/relational/table.cxx
Examining data/odb-2.4.0/odb/semantics/relational/primary-key.cxx
Examining data/odb-2.4.0/odb/semantics/relational/model.cxx
Examining data/odb-2.4.0/odb/semantics/relational/key.cxx
Examining data/odb-2.4.0/odb/semantics/relational/index.cxx
Examining data/odb-2.4.0/odb/semantics/relational/foreign-key.cxx
Examining data/odb-2.4.0/odb/semantics/relational/elements.cxx
Examining data/odb-2.4.0/odb/semantics/relational/column.cxx
Examining data/odb-2.4.0/odb/semantics/relational/changeset.cxx
Examining data/odb-2.4.0/odb/semantics/relational/changelog.cxx
Examining data/odb-2.4.0/odb/semantics/elements.cxx
Examining data/odb-2.4.0/odb/relational/schema-source.cxx
Examining data/odb-2.4.0/odb/relational/schema.cxx
Examining data/odb-2.4.0/odb/relational/model.cxx
Examining data/odb-2.4.0/odb/relational/source.cxx
Examining data/odb-2.4.0/odb/relational/inline.cxx
Examining data/odb-2.4.0/odb/relational/header.cxx
Examining data/odb-2.4.0/odb/relational/processor.cxx
Examining data/odb-2.4.0/odb/relational/context.cxx
Examining data/odb-2.4.0/odb/relational/common-query.cxx
Examining data/odb-2.4.0/odb/relational/common.cxx
Examining data/odb-2.4.0/odb/relational/changelog.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/schema.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/model.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/source.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/inline.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/header.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/context.cxx
Examining data/odb-2.4.0/odb/relational/sqlite/common.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/schema.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/model.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/source.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/inline.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/header.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/context.cxx
Examining data/odb-2.4.0/odb/relational/pgsql/common.cxx
Examining data/odb-2.4.0/odb/relational/oracle/schema.cxx
Examining data/odb-2.4.0/odb/relational/oracle/model.cxx
Examining data/odb-2.4.0/odb/relational/oracle/source.cxx
Examining data/odb-2.4.0/odb/relational/oracle/inline.cxx
Examining data/odb-2.4.0/odb/relational/oracle/header.cxx
Examining data/odb-2.4.0/odb/relational/oracle/context.cxx
Examining data/odb-2.4.0/odb/relational/oracle/common.cxx
Examining data/odb-2.4.0/odb/relational/mysql/schema.cxx
Examining data/odb-2.4.0/odb/relational/mysql/model.cxx
Examining data/odb-2.4.0/odb/relational/mysql/source.cxx
Examining data/odb-2.4.0/odb/relational/mysql/inline.cxx
Examining data/odb-2.4.0/odb/relational/mysql/header.cxx
Examining data/odb-2.4.0/odb/relational/mysql/context.cxx
Examining data/odb-2.4.0/odb/relational/mysql/common.cxx
Examining data/odb-2.4.0/odb/relational/mssql/schema.cxx
Examining data/odb-2.4.0/odb/relational/mssql/model.cxx
Examining data/odb-2.4.0/odb/relational/mssql/source.cxx
Examining data/odb-2.4.0/odb/relational/mssql/inline.cxx
Examining data/odb-2.4.0/odb/relational/mssql/header.cxx
Examining data/odb-2.4.0/odb/relational/mssql/context.cxx
Examining data/odb-2.4.0/odb/relational/mssql/common.cxx
Examining data/odb-2.4.0/odb/relational/validator.cxx
Examining data/odb-2.4.0/odb/context.cxx
Examining data/odb-2.4.0/odb/generator.cxx
Examining data/odb-2.4.0/odb/processor.cxx
Examining data/odb-2.4.0/odb/validator.cxx
Examining data/odb-2.4.0/odb/cxx-lexer.cxx
Examining data/odb-2.4.0/odb/include.cxx
Examining data/odb-2.4.0/odb/plugin.cxx
Examining data/odb-2.4.0/odb/parser.cxx
FINAL RESULTS:
data/odb-2.4.0/odb/cxx-lexer.cxx:193:5: [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.
vfprintf (stderr, msg, *ap);
data/odb-2.4.0/odb/odb.cxx:1660:9: [4] (shell) execvp:
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.
if (execvp (args[0], const_cast<char**> (&args[0])) == -1)
data/odb-2.4.0/odb/parser.cxx:33:22: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
typedef semantics::access access;
data/odb-2.4.0/odb/parser.cxx:33:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
typedef semantics::access access;
data/odb-2.4.0/odb/parser.cxx:100:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access,
data/odb-2.4.0/odb/parser.cxx:109:20: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
emit_type (tree, access, path const& f, size_t l, size_t c);
data/odb-2.4.0/odb/parser.cxx:112:22: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
create_type (tree, access, path const& f, size_t l, size_t c);
data/odb-2.4.0/odb/parser.cxx:149:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access
data/odb-2.4.0/odb/parser.cxx:155:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access::private_;
data/odb-2.4.0/odb/parser.cxx:158:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access::protected_;
data/odb-2.4.0/odb/parser.cxx:160:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access::public_;
data/odb-2.4.0/odb/parser.cxx:253:5: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access a (access::public_);
data/odb-2.4.0/odb/parser.cxx:253:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access a (access::public_);
data/odb-2.4.0/odb/parser.cxx:261:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
a = access::public_;
data/odb-2.4.0/odb/parser.cxx:265:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
a = access::protected_;
data/odb-2.4.0/odb/parser.cxx:270:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
a = access::private_;
data/odb-2.4.0/odb/parser.cxx:297:26: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
emit_type (base, access::public_, file, line, clmn));
data/odb-2.4.0/odb/parser.cxx:407:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access a (access::public_);
data/odb-2.4.0/odb/parser.cxx:407: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
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access a (access::public_);
data/odb-2.4.0/odb/parser.cxx:496:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access a (decl_access (d));
data/odb-2.4.0/odb/parser.cxx:668:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access a (decl_access (d));
data/odb-2.4.0/odb/parser.cxx:1440:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access access,
data/odb-2.4.0/odb/parser.cxx:1440:19: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access access,
data/odb-2.4.0/odb/parser.cxx:1507:55: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
unit_->new_edge<names> (*e_node, er_node, name, access::public_);
data/odb-2.4.0/odb/parser.cxx:1513:55: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
unit_->new_edge<names> (*scope_, er_node, name, access);
data/odb-2.4.0/odb/parser.cxx:1524:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access access,
data/odb-2.4.0/odb/parser.cxx:1524:19: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access access,
data/odb-2.4.0/odb/parser.cxx:1544:30: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
: create_type (t, access, file, line, clmn));
data/odb-2.4.0/odb/parser.cxx:1647:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access access,
data/odb-2.4.0/odb/parser.cxx:1647: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
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access access,
data/odb-2.4.0/odb/parser.cxx:1796:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
r = &emit_enum (t, access, file, line, clmn);
data/odb-2.4.0/odb/parser.cxx:1807:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
r = &emit_enum (t, access, f, l, c, true);
data/odb-2.4.0/odb/parser.cxx:1864:40: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
type& bt_node (emit_type (bt_mv, access::public_, file, line, clmn));
data/odb-2.4.0/odb/parser.cxx:1883:37: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
type& bt_node (emit_type (bt, access::public_, file, line, clmn));
data/odb-2.4.0/odb/parser.cxx:1903:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
type& bt_node (emit_type (bt, access::public_, file, line, clmn));
data/odb-2.4.0/odb/plugin.cxx:180:7: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (s, d.string ().c_str ());
data/odb-2.4.0/odb/plugin.cxx:205:7: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (p, f.c_str ());
data/odb-2.4.0/odb/processor.cxx:352:20: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
semantics::access const& a (m.named ().access ());
data/odb-2.4.0/odb/processor.cxx:352:48: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
semantics::access const& a (m.named ().access ());
data/odb-2.4.0/odb/processor.cxx:360:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!virt && (a == semantics::access::public_ ||
data/odb-2.4.0/odb/processor.cxx:1899:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = TREE_TYPE (access);
data/odb-2.4.0/odb/processor.cxx:1904:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access, get_identifier ("container_traits"), true, false);
data/odb-2.4.0/odb/processor.cxx:2301:34: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
np, m, idm->name (), access::public_);
data/odb-2.4.0/odb/processor.cxx:2350:31: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
np, m, "typeid_", access::public_);
data/odb-2.4.0/odb/semantics/class.cxx:13:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
inherits (access_type access, bool virt)
data/odb-2.4.0/odb/semantics/class.cxx:14:32: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
: virt_ (virt), access_ (access)
data/odb-2.4.0/odb/semantics/elements.cxx:23:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
char const* access::
data/odb-2.4.0/odb/odb.cxx:184: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.
if (char const* s = getenv (name))
data/odb-2.4.0/odb/odb.cxx:1399:23: [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.
if (char const* s = getenv ("PATH"))
data/odb-2.4.0/odb/option-types.cxx:45:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:101:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:145:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:188:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:217:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:253:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:295:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/option-types.cxx:337:10: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/semantics/relational/deferrable.cxx:50:14: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/semantics/relational/foreign-key.cxx:33:12: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/semantics/relational/foreign-key.cxx:44:14: [3] (random) setstate:
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.
is.setstate (istream::failbit);
data/odb-2.4.0/odb/context.cxx:2114: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 c (fq[i]);
data/odb-2.4.0/odb/context.cxx:2143: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 c (name[i]);
data/odb-2.4.0/odb/context.cxx:2212: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 c1 (s[i]);
data/odb-2.4.0/odb/context.cxx:2213: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 c2 (s[i + 1]);
data/odb-2.4.0/odb/context.cxx:2743:59: [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).
process_include_path (string const& ip, bool prefix, char open)
data/odb-2.4.0/odb/generator.cxx:54:3: [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 (ifstream& ifs, path const& p)
data/odb-2.4.0/odb/generator.cxx:56: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).
ifs.open (p.string ().c_str (), ios_base::in | ios_base::binary);
data/odb-2.4.0/odb/generator.cxx:66:3: [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 (ofstream& ofs, path const& p, ios_base::openmode m = ios_base::out)
data/odb-2.4.0/odb/generator.cxx:68: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).
ofs.open (p.string ().c_str (), ios_base::out | m);
data/odb-2.4.0/odb/generator.cxx:91: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 (ifs, file);
data/odb-2.4.0/odb/generator.cxx:225: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).
log.open (in_log_path.string ().c_str (),
data/odb-2.4.0/odb/generator.cxx:367:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
open (hxx, hxx_path);
data/odb-2.4.0/odb/generator.cxx:376:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
open (ixx, ixx_path);
data/odb-2.4.0/odb/generator.cxx:385:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
open (cxx, cxx_path);
data/odb-2.4.0/odb/generator.cxx:398:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
open (sch, sch_path);
data/odb-2.4.0/odb/generator.cxx:409:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
open (sql, sql_path);
data/odb-2.4.0/odb/generator.cxx:423: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).
open (*pre, mig_pre_paths[i]);
data/odb-2.4.0/odb/generator.cxx:427: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).
open (*post, mig_post_paths[i]);
data/odb-2.4.0/odb/generator.cxx:967: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).
open (log, out_log_path, ios_base::binary);
data/odb-2.4.0/odb/include.cxx:374: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 c (l[i]);
data/odb-2.4.0/odb/odb.cxx:802:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
ifs.open (name.c_str (), ios_base::in | ios_base::binary);
data/odb-2.4.0/odb/options.cxx:368: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.
char c (line[p]);
data/odb-2.4.0/odb/options.cxx:379: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 cf (s2[0]), cl (s2[n - 1]);
data/odb-2.4.0/odb/pragma.cxx:130: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 c (str[i]);
data/odb-2.4.0/odb/pragma.cxx:243:13: [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[256];
data/odb-2.4.0/odb/pragma.cxx:2224:15: [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[256];
data/odb-2.4.0/odb/relational/changelog.cxx:106:59: [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).
else if (ops.warn_hard_add () && version->open)
data/odb-2.4.0/odb/relational/changelog.cxx:166:62: [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).
else if (ops.warn_hard_delete () && version->open)
data/odb-2.4.0/odb/relational/changelog.cxx:596:59: [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).
else if (ops.warn_hard_add () && version->open)
data/odb-2.4.0/odb/relational/changelog.cxx:680:62: [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).
else if (ops.warn_hard_delete () && version->open)
data/odb-2.4.0/odb/relational/changelog.cxx:1037:17: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if (!mv.open)
data/odb-2.4.0/odb/relational/changelog.cxx:1190:15: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
if (!mv.open)
data/odb-2.4.0/odb/semantics/relational/name.cxx:49: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 c (s[i]);
data/odb-2.4.0/odb/plugin.cxx:351: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).
string opt (strlen (a.key) > 1 ? "--" : "-");
ANALYSIS SUMMARY:
Hits = 94
Lines analyzed = 56840 in approximately 1.12 seconds (50928 lines/second)
Physical Source Lines of Code (SLOC) = 41219
Hits@level = [0] 2 [1] 1 [2] 33 [3] 13 [4] 47 [5] 0
Hits@level+ = [0+] 96 [1+] 94 [2+] 93 [3+] 60 [4+] 47 [5+] 0
Hits/KSLOC@level+ = [0+] 2.32902 [1+] 2.2805 [2+] 2.25624 [3+] 1.45564 [4+] 1.14025 [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.