linux poison RSS
linux poison Email

Examines Source Code and Look for Security Weaknesses - Flawfinder

Flawfinder searches through C/C++ source code looking for potential security flaws and produces a report describing the potential flaws found in source code, ranking them by likely severity.

Flawfinder works by using a built-in database of C/C++ functions with well-known problems, such as buffer overflow risks (e.g., strcpy(), strcat(), gets(), sprintf(), and the scanf() family), format string problems ([v][f]printf(), [v]snprintf(), and syslog()), race conditions (such as access(), chown(), chgrp(), chmod(), tmpfile(), tmpnam(), tempnam(), and mktemp()), potential shell metacharacter dangers (most of the exec() family, system(), popen()), and poor random number acquisition (such as random()). The good thing is that you don't have to create this database - it comes with the tool.

Flawfinder then takes the source code text, and matches the source code text against those names, while ignoring text inside comments and strings (except for flawfinder directives). Flawfinder also knows about gettext (a common library for internationalized programs), and will treat constant strings passed through gettext as though they were constant strings; this reduces the number of false hits in internationalized programs.

Flawfinder can also generate differential reports by pointing it to a patch (diff) file describing the code changes. This way it can be used to determine if the potential flaws found in code have increased or decreased after a commit to a source code management system like CVS or Subversion.

Flawfinder Installation:
Ubuntu users can quickly download and install flawfinder using apt-get
sudo apt-get install flawfinder
Using Flawfinder:
Flawfinder is an command line utility, open the terminal and type following command to scan any given C/C++ source file:
flawfinder --html test.c
Above command will generate the report in the required HTML format


Flawfinder will produce a list of ``hits'' (potential security flaws), sorted by risk; the riskiest hits are shown first.  The risk level is shown inside square brackets and varies from 0, very little risk, to 5, great risk.  This risk level depends not only on the function, but on the values of the parameters of the function.  For example, con‐stant strings are often less risky than fully variable strings in many contexts, and in those contexts the hit will have a lower risk level.  Flawfinder knows about  gettext (a  common  library  for  internationalized programs) and will treat constant strings passed through gettext as though they were constant strings; this reduces the number of false hits in internationalized programs.  Flawfinder will do the same sort of thing with _T() and _TEXT(), common Microsoft macros for handling  internationalized  programs Flawfinder  correctly  ignores  most  text  inside  comments and strings.  Normally flawfinder shows all hits with a risk level of at least 1, but you can use the --minlevel option to show only hits with higher risk levels if you wish.




0 comments:

Post a Comment

Related Posts with Thumbnails