Python based C/C++ static code flaw finder
http://www.dwheeler.com/flawfinder/
program that examines source code and reports possible security weaknesses (``flaws'') sorted by risk level. It's very useful for quickly finding and removing at least some potential security problems before a program is widely released to the public.
- Developed at devel:tools
- Sources inherited from project openSUSE:Factory
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:15.2:FactoryCandidates/flawfinder && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| flawfinder-2.0.15.tar.gz | 0000253677 248 KB | |
| flawfinder.changes | 0000003818 3.73 KB | |
| flawfinder.spec | 0000001599 1.56 KB |
Revision 3 (latest revision is 7)
Dominique Leuenberger (dimstar_suse)
accepted
request 862538
from
Michael Vetter (jubalh)
(revision 3)
- Update to 2.0.15:
* Fixed some release problems in 2.0.14. (#30)
* Improved handling of LoadLibraryEx; flawfinderr no longer complains
about certain constructs that are known to be safe (eliminating
some false positives).
- Update to 2.0.14:
* If there are >0 hits, tell users how to ignore them as part of the
tool output.
* Various Windows improvments.
Ignore LoadLibraryEx if its third parameter is
LOAD_LIBRARY_SEARCH_SYSTEM32, as this is safe, and
remove the rule for InitialCriticalSection
(this is no longer a vulnerability on current widely-used versions
of Windows)
* Various C++ improvements. Add .hpp support for C++,
ignore "system::" to reduce false positives,
treat ' as digit separator when file extension is a C++ file
(for C++14).
* I had some release problems; this is identified as 2.0.14
(skipping a few minor numbers) to ensure that the version
number uniquely identifies a specific release.
Comments 0