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/dbus-cpp-5.0.1/examples/benchmark/benchmark_service.h
Examining data/dbus-cpp-5.0.1/examples/benchmark/main.cpp
Examining data/dbus-cpp-5.0.1/examples/geoclue/geoclue.h
Examining data/dbus-cpp-5.0.1/examples/geoclue/main.cpp
Examining data/dbus-cpp-5.0.1/examples/ofono/main.cpp
Examining data/dbus-cpp-5.0.1/examples/upower/main.cpp
Examining data/dbus-cpp-5.0.1/examples/upower/upower.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/announcer.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/argument_type.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/asio/executor.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/bus.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/codec.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/compiler.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/dbus.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/error.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/executor.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/fixture.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/generator.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/generator_configuration.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/helper/apply_visitor.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/helper/is_compound_type.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/helper/signature.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/helper/type_mapper.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/impl/message.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/impl/object.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/impl/property.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/impl/signal.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/interfaces/introspectable.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/interfaces/object_manager.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/interfaces/properties.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/introspection_parser.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/lifetime_constrained_cache.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/macros.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/match_rule.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/message.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/message_factory.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/message_router.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/message_streaming_operators.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/object.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/pending_call.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/property.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/resolver.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/result.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/service.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/service_watcher.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/signal.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/skeleton.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/stub.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/traits/service.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/traits/timeout.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/traits/watch.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/any.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/object_path.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/signature.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/stl/list.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/stl/map.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/stl/string.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/stl/tuple.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/stl/vector.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/struct.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/unix_fd.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/types/variant.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/visibility.h
Examining data/dbus-cpp-5.0.1/include/core/dbus/well_known_bus.h
Examining data/dbus-cpp-5.0.1/src/core/dbus/asio/executor.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/bus.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/compiler.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/compiler_main.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/dbus.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/error.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/introspection_parser.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/match_rule.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/message.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/message_factory_impl.h
Examining data/dbus-cpp-5.0.1/src/core/dbus/message_impl.h
Examining data/dbus-cpp-5.0.1/src/core/dbus/message_p.h
Examining data/dbus-cpp-5.0.1/src/core/dbus/pending_call_impl.h
Examining data/dbus-cpp-5.0.1/src/core/dbus/service.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/service_watcher.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/types/object_path.cpp
Examining data/dbus-cpp-5.0.1/src/core/dbus/generator.cpp
Examining data/dbus-cpp-5.0.1/tests/bus_test.cpp
Examining data/dbus-cpp-5.0.1/tests/cache_test.cpp
Examining data/dbus-cpp-5.0.1/tests/codec_test.cpp
Examining data/dbus-cpp-5.0.1/tests/compiler_test.cpp
Examining data/dbus-cpp-5.0.1/tests/dbus_test.cpp
Examining data/dbus-cpp-5.0.1/tests/executor_test.cpp
Examining data/dbus-cpp-5.0.1/tests/match_rule_test.cpp
Examining data/dbus-cpp-5.0.1/tests/message_router_test.cpp
Examining data/dbus-cpp-5.0.1/tests/message_test.cpp
Examining data/dbus-cpp-5.0.1/tests/service_test.cpp
Examining data/dbus-cpp-5.0.1/tests/service_watcher_test.cpp
Examining data/dbus-cpp-5.0.1/tests/sig_term_catcher.h
Examining data/dbus-cpp-5.0.1/tests/signal_delivery_test.cpp
Examining data/dbus-cpp-5.0.1/tests/stl_codec_test.cpp
Examining data/dbus-cpp-5.0.1/tests/test_main.cpp
Examining data/dbus-cpp-5.0.1/tests/test_service.h
Examining data/dbus-cpp-5.0.1/tests/test_service_tiny.h
Examining data/dbus-cpp-5.0.1/tests/types_test.cpp
Examining data/dbus-cpp-5.0.1/tests/async_execution_load_test.cpp
FINAL RESULTS:
data/dbus-cpp-5.0.1/examples/upower/main.cpp:47:88: [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.
static dbus::Bus::Ptr system_bus = std::make_shared<dbus::Bus>(dbus::WellKnownBus::system);
data/dbus-cpp-5.0.1/include/core/dbus/introspection_parser.h:133:16: [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; ///< Access specification.
data/dbus-cpp-5.0.1/src/core/dbus/asio/executor.cpp:132:48: [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.
timer.async_wait([wp](const boost::system::error_code& ec)
data/dbus-cpp-5.0.1/src/core/dbus/asio/executor.cpp:152:38: [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.
void on_timeout(const boost::system::error_code& ec)
data/dbus-cpp-5.0.1/src/core/dbus/asio/executor.cpp:198:92: [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.
stream_descriptor.async_read_some(boost::asio::null_buffers(), [wp](boost::system::error_code ec, std::size_t bytes_transferred)
data/dbus-cpp-5.0.1/src/core/dbus/asio/executor.cpp:212:93: [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.
stream_descriptor.async_write_some(boost::asio::null_buffers(), [wp](boost::system::error_code ec, std::size_t bytes_transferred)
data/dbus-cpp-5.0.1/src/core/dbus/asio/executor.cpp:236:65: [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.
void on_stream_descriptor_event(int event, const boost::system::error_code& error, std::size_t)
data/dbus-cpp-5.0.1/src/core/dbus/generator.cpp:755: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.
switch(element.property().access)
data/dbus-cpp-5.0.1/examples/benchmark/main.cpp:165: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).
out.open("dbus_benchmark_vector_int32_t.txt");
data/dbus-cpp-5.0.1/src/core/dbus/generator.cpp:663:61: [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).
context.namespaces.node.interface.protocol_file.open(
data/dbus-cpp-5.0.1/examples/benchmark/main.cpp:77:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!read(fds[read_fd], std::addressof(value), sizeof(value)))
data/dbus-cpp-5.0.1/include/core/dbus/introspection_parser.h:126:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read, ///< Property is readable.
data/dbus-cpp-5.0.1/src/core/dbus/generator.cpp:757:57: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
case IntrospectionParser::Property::Access::read:
data/dbus-cpp-5.0.1/src/core/dbus/introspection_parser.cpp:226:48: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
{"read", Property::Access::read},
data/dbus-cpp-5.0.1/tests/codec_test.cpp:297:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
EXPECT_TRUE(read(fd.to_int(), std::addressof(result), sizeof(result)) >= 0);
ANALYSIS SUMMARY:
Hits = 15
Lines analyzed = 17345 in approximately 0.45 seconds (38207 lines/second)
Physical Source Lines of Code (SLOC) = 11439
Hits@level = [0] 0 [1] 5 [2] 2 [3] 0 [4] 8 [5] 0
Hits@level+ = [0+] 15 [1+] 15 [2+] 10 [3+] 8 [4+] 8 [5+] 0
Hits/KSLOC@level+ = [0+] 1.3113 [1+] 1.3113 [2+] 0.874202 [3+] 0.699362 [4+] 0.699362 [5+] 0
Dot directories skipped = 2 (--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.