All Projects → intel → Cve Bin Tool

intel / Cve Bin Tool

Licence: gpl-3.0
This tool scans for a number of common, vulnerable components (openssl, libpng, libxml2, expat and a few others) to let you know if your system includes common libraries with known vulnerabilities.

Projects that are alternatives of or similar to Cve Bin Tool

CVE Alerting Platform
Stars: ✭ 384 (+81.99%)
Mutual labels:  vulnerabilities, cve
Dependency spy
Find known vulnerabilities in your dependencies
Stars: ✭ 87 (-58.77%)
Mutual labels:  hacktoberfest, vulnerabilities
Performing security tests inside your CI
Stars: ✭ 398 (+88.63%)
Mutual labels:  hacktoberfest, vulnerabilities
Kube Hunter
Hunt for security weaknesses in Kubernetes clusters
Stars: ✭ 3,399 (+1510.9%)
Mutual labels:  hacktoberfest, vulnerabilities
Awesome Vulnerable
Stars: ✭ 133 (-36.97%)
Mutual labels:  hacktoberfest, vulnerabilities
快速搭建各种漏洞环境(Various vulnerability environment)
Stars: ✭ 3,353 (+1489.1%)
Mutual labels:  vulnerabilities, cve
Vulmap 是一款 web 漏洞扫描和验证工具, 可对 webapps 进行漏洞扫描, 并且具备漏洞利用功能
Stars: ✭ 1,079 (+411.37%)
Mutual labels:  vulnerabilities, cve
Open-Source Vulnerability Intelligence Center - Unified source of vulnerability, exploit and threat Intelligence feeds
Stars: ✭ 66 (-68.72%)
Mutual labels:  vulnerabilities, cve
Cve Search
cve-search - a tool to perform local searches for known vulnerabilities
Stars: ✭ 1,765 (+736.49%)
Mutual labels:  vulnerabilities, cve
cvebase is a community-driven vulnerability data platform to discover the world's top security researchers and their latest disclosed vulnerabilities & PoCs
Stars: ✭ 88 (-58.29%)
Mutual labels:  vulnerabilities, cve
This repository contains writeups for various CTFs I've participated in (Including Hack The Box).
Stars: ✭ 61 (-71.09%)
Mutual labels:  vulnerabilities, cve
Sbt Dependency Check
SBT Plugin for OWASP DependencyCheck. Monitor your dependencies and report if there are any publicly known vulnerabilities (e.g. CVEs). 🌈
Stars: ✭ 187 (-11.37%)
Mutual labels:  vulnerabilities, cve
A Common Weakness Enumeration (CWE) Node.js SDK compliant with MITRE / CAPEC
Stars: ✭ 18 (-91.47%)
Mutual labels:  vulnerabilities, cve
Horusec is an open source tool that improves identification of vulnerabilities in your project with just one command.
Stars: ✭ 311 (+47.39%)
Mutual labels:  hacktoberfest, vulnerabilities
PocOrExp in Github
聚合Github上已有的Poc或者Exp,CVE信息来自CVE官网。Auto Collect Poc Or Exp from Github by CVE ID.
Stars: ✭ 544 (+157.82%)
Mutual labels:  vulnerabilities, cve
WPScan rewritten in Python + some WPSeku ideas
Stars: ✭ 456 (+116.11%)
Mutual labels:  hacktoberfest, vulnerabilities
Bug's feed is a local hosted portal where you can search for the latest news, videos, CVEs, vulnerabilities...
Stars: ✭ 90 (-57.35%)
Mutual labels:  vulnerabilities, cve
Multi source CVE/exploit parser.
Stars: ✭ 25 (-88.15%)
Mutual labels:  vulnerabilities, cve
PatrowlHears - Vulnerability Intelligence Center / Exploits
Stars: ✭ 89 (-57.82%)
Mutual labels:  vulnerabilities, cve
Vulnerability (CVE) scanner for Nix/NixOS.
Stars: ✭ 161 (-23.7%)
Mutual labels:  vulnerabilities, cve

CVE Binary Tool quick start / README

Build Status codecov Gitter On ReadTheDocs On PyPI Code style: black Imports: isort

The CVE Binary Tool scans for a number of common, vulnerable open source components such as openssl, libpng, libxml2, and expat to let you know if a given directory or binary file includes common libraries with known vulnerabilities., known as CVEs (Common Vulnerabilities and Exposures).

See our documentation and quickstart guide
Usage: cve-bin-tool <directory/file to scan>

You can also do python -m cve_bin_tool.cli which is useful if you're trying the latest code from the cve-bin-tool github.

optional arguments:
  -e, --exclude         exclude path while scanning
  -h, --help            show this help message and exit
  -V, --version         show program's version number and exit
  -u {now,daily,never,latest}, --update {now,daily,never,latest}
                        update schedule for NVD database (default: daily)
                        skips checking for a new version
  directory             directory to scan
  -i INPUT_FILE, --input-file INPUT_FILE
                        provide input filename
  -C CONFIG, --config CONFIG
                        provide config file

  -q, --quiet           suppress output
  -l {debug,info,warning,error,critical}, --log {debug,info,warning,error,critical}
                        log level (default: info)
  -o OUTPUT_FILE, --output-file OUTPUT_FILE
                        provide output filename (default: output to stdout)
  --html-theme HTML_THEME
                        provide custom theme directory for HTML Report
  -f {csv,json,console,html}, --format {csv,json,console,html}
                        update output format (default: console)
  -c CVSS, --cvss CVSS  minimum CVSS score (as integer in range 0 to 10) to
                        report (default: 0)
  -S {low,medium,high,critical}, --severity {low,medium,high,critical}
                        minimum CVE severity to report (default: low)

  -s SKIPS, --skips SKIPS
                        comma-separated list of checkers to disable
  -r RUNS, --runs RUNS  comma-separated list of checkers to enable

   -x, --extract        autoextract compressed files
   CVE Binary Tool autoextracts all compressed files by default now

Note that if the CVSS and Severity flags are both specified, the CVSS flag takes precedence.

--input-file extends the functionality of csv2cve for other formats like JSON. It also allows cve-bin-tool to specify triage data so you can group issues which may have been mitigated (through patches, configuration, or other methods not detectable by our version scanning method) or mark false positives. Triage data can be re-used and applied to multiple scans. You can provide either CSV or JSON file as input_file with vendor, product and version fields. You can also add optional fields like remarks, comments, cve_number, severity.

Note that you can use -i or --input-file option to produce list of CVEs found in given vendor, product and version fields (Usage: cve-bin-tool -i=test.csv) or supplement extra triage data like remarks, comments etc. while scanning directory so that output will reflect this triage data and you can save time of re-triaging (Usage: cve-bin-tool -i=test.csv /path/to/scan).

Note: For backward compatibility, we still support csv2cve command for producing CVEs from csv but we recommend using new --input-file command instead.

You can use --config option to provide configuration file for the tool. You can still override options specified in config file with command line arguments. See our sample config files in the test/config

The 0.3.1 release is intended to be the last release to officially support python 2.7; please switch to python 3.6+ for future releases and to use the development tree. You can check our CI configuration to see what versions of python we're explicitly testing.

If you want to integrate cve-bin-tool as a part of your github action pipeline. You can checkout our example github action.

This readme is intended to be a quickstart guide for using the tool. If you require more information, there is also a user manual available.

How it works

This scanner looks at the strings found in binary files to see if they match certain vulnerable versions of the following libraries and tools:

Available checkers
avahi bash bind binutils busybox bzip2 cups
curl dovecot expat ffmpeg freeradius gcc gimp
gnutls glibc gstreamer haproxy hostapd icecast icu
irssi kerberos libarchive libdb libgcrypt libjpeg libnss
libtiff libvirt lighttpd mariadb memcached ncurses nessus
netpbm nginx node openafs openldap openssh openssl
openswan openvpn png polarssl_fedora postgresql python qt
radare2 rsyslog samba sqlite strongswan syslogng systemd
tcpdump varnish wireshark xerces xml2 zlib

All the checkers can be found in the checkers directory, as can the instructions on how to add a new checker. Support for new checkers can be requested via GitHub issues.


This scanner does not attempt to exploit issues or examine the code in greater detail; it only looks for library signatures and version numbers. As such, it cannot tell if someone has backported fixes to a vulnerable version, and it will not work if library or version information was intentionally obfuscated.

This tool is meant to be used as a quick-to-run, easily-automatable check in a non-malicious environment so that developers can be made aware of old libraries with security issues that have been compiled into their binaries.


To use the auto-extractor, you may need the following utilities depending on the type of file you need to extract. The utilities below are required to run the full test suite on Linux:

  • file
  • strings
  • tar
  • unzip
  • rpm2cpio
  • cpio
  • ar
  • cabextract

Most of these are installed by default on many Linux systems, but cabextract and rpm2cpio in particular might need to be installed.

On windows systems, you may need:

  • ar
  • 7z
  • Expand

Windows has ar and Expand installed in default, but 7z in particular might need to be installed. If you want to run our test-suite or scan a zstd compressed file, We recommend installing this 7-zip-zstd fork of 7zip. We are currently using 7z for extracting jar, apk, msi, exe and rpm files.

If you get an error about building libraries when you try to install from pip, you may need to install the Windows build tools. The Windows build tools are available for free from

If you get an error while installing brotlipy on Windows, installing the compiler above should fix it.

Feedback & Contributions

Bugs and feature requests can be made via GitHub issues. Be aware that these issues are not private, so take care when providing output to make sure you are not disclosing security issues in other products.

Pull requests are also welcome via git.

The CVE Binary Tool uses the Black python code formatter and isort to keep coding style consistent; you may wish to have it installed to make pull requests easier. We've provided a pre-commit hook (in .pre-commit.config.yaml) so if you want to have the check run locally before you commit, you can install pre-commit and install the hook as follows from the main cve-bin-tool directory:

pip install pre-commit
pre-commit install

Security Issues

Security issues with the tool itself can be reported to Intel's security incident response team via

If in the course of using this tool you discover a security issue with someone else's code, please disclose responsibly to the appropriate party.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].