kernel-hardening.lists.openwall.com archive mirror
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: oss-security@lists.openwall.com, kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Security vulnerability tools
Date: Wed, 27 Mar 2013 15:54:04 -0400	[thread overview]
Message-ID: <51534E5C.8070303@linux.vnet.ibm.com> (raw)

Hi,

I'd like to get a better understanding of tools used in the open source 
community (kernel and user space) to detect security vulnerabilities.

I have a list below to get started.  If anyone has any input, I'd 
appreciate it!

I'll plan on updating http://oss-security.openwall.org/wiki/tools with 
anything it doesn't already have.

pscan
-----
Scans C/C++ source code for problematic uses of printf style functions

rats
----
Rough auditing tool for security.  A general purpose scanner for 
detecting potential security problems in a wide range of languages.

flawfinder
----------
A general purpose scanner for finding and reporting upon potential flaws 
in both C and C++ source code

Valgrind
--------
Detect many memory management and threading bugs, and profile your 
programs in detail

KEDR
----
Provides runtime analysis of Linux kernel modules including device 
drivers, file system modules, etc

kmemcheck, kmemleak
-------------------
Linux Kernel debugging features for detecting memory issues

Smatch
------
A static analysis tool for C

Coverity
--------
Provides static analysis tools for C, C++, and other languages (requires 
license, Red Hat has one)

Coccinelle
----------
A tool for matching and fixing source code for C, C++, and other languages

Clang
-----
Static analysis tool for C/C++

Metasploit
----------
Used for identifying security issues. It includes many capabilities, 
including fuzzer support

Trinity
-------
A Linux system call fuzzer

fsfuzzer
--------
File system fuzzer

scapy
-----
Network packet fuzzer

-- 
Regards,
Corey Bryant

             reply	other threads:[~2013-03-27 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 19:54 Corey Bryant [this message]
2013-03-27 19:58 ` [kernel-hardening] Security vulnerability tools Tim Brown
2013-03-27 20:12 ` [kernel-hardening] " Solar Designer
2013-03-27 21:17   ` Corey Bryant
2013-03-28  7:32     ` Solar Designer
2013-04-08  5:37       ` Hasinoliva MIARIMANJATO
2013-03-27 20:31 ` [kernel-hardening] Re: [oss-security] " Russ Allbery

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51534E5C.8070303@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=oss-security@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).