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/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/nnp-test/nnp-test.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/acct.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/ns.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/raw.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/setgid.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/setuid.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/socket.c Examining data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/userns.c FINAL RESULTS: data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/ns.c:22:6: [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->argv[0], args->argv) != 0) { data/containerd-1.4.1~ds1/vendor/github.com/docker/docker/contrib/syscall-test/userns.c:22:6: [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->argv[0], args->argv) != 0) { ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 218 in approximately 0.20 seconds (1073 lines/second) Physical Source Lines of Code (SLOC) = 179 Hits@level = [0] 10 [1] 0 [2] 0 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 12 [1+] 2 [2+] 2 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 67.0391 [1+] 11.1732 [2+] 11.1732 [3+] 11.1732 [4+] 11.1732 [5+] 0 Dot directories skipped = 3 (--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.