Skip to content

Releases: intel/cve-bin-tool

v3.1.pre0

21 Mar 17:02
295b6d1
Compare
Choose a tag to compare
v3.1.pre0 Pre-release
Pre-release

CVE Binary Tool 3.1.pre0

Pre-release for what will eventually be 3.1. There are a few PRs still in progress, and you can see what remains to be updated in the 3.1 milestone. The release notes below are auto-generated by GitHub.

What's Changed

New Contributors

Full Changelog: v3.0...v3.1.pre0

CVE Binary Tool 3.0

15 Dec 00:59
0f0e2c0
Compare
Choose a tag to compare

CVE Binary Tool 3.0

The CVE Binary Tool 3.0 release includes improved tools for checking known lists of packages including Linux distributions, improved methods of communication with NVD to get vulnerability data, additional checkers, and significant refactoring to streamline the output.

New feature highlights:

  • SBOM Scanning: CVE Binary Tool can now take Software Bill of Materials (SBOM) files to help users improve their supply chain security data for all known dependencies. The initial feature can handle some versions of SPDX, CycloneDX and SWID formats. More information on SBOM scanning can be found here: https://github.com/intel/cve-bin-tool/blob/main/doc/how_to_guides/sbom.md
  • Known vulnerability information: Users scanning some linux distro packages can now get additional information about fixes available for those platforms.
  • Vulnerability Data: The default method for getting NVD vulnerability lists has been changed. Previously we downloaded full yearly JSON files if anything in the year had changed, the new API allows us to get only the latest changes. Users may see a speedup during the update phase as a result.
  • (Breaking change) Return codes: The return codes used by CVE Binary Tool have changed.
    • A 0 will be returned if no CVEs are found, a 1 will be returned if any CVEs were found (no matter how many), and codes 2+ indicate operational errors. A full list of error codes is available here: https://github.com/intel/cve-bin-tool/blob/main/cve_bin_tool/error_handler.py
    • Previously we returned the number of CVEs found, but this could exceed the expected range for return codes and cause unexpected behaviour.

Thanks especially to our 2021 GSoC students, @BreadGenie, @imsahil007 and @peb-peb whose final GSoC contributions are part of this release.

A full list of changes are below. Commit messages use the Conventional Commits format.

What's Changed Since 2.2

Read more

CVE Binary Tool 3.0.pre1

24 Nov 17:28
5b14b1b
Compare
Choose a tag to compare
Pre-release

Pre-release for what will hopefully be 3.0. The release notes below are auto-generated by github and it looks like it went a bit too far back in its comparison, but I'm sharing it so everyone can see what the auto-generated output looks like.

What's Changed

Read more

CVE Binary Tool 2.2.1

04 Aug 19:00
Compare
Choose a tag to compare

The 2.2.1 release relaxes the behaviour when file extraction fails, which was causing problems for some users scanning files with .exe and .apk file extensions using the previous release. In 2.2 all extraction fails caused the tool to halt and throw an exception, in 2.2.1 the tool will log a warning and continue.

CVE Binary Tool 2.2

09 Jul 01:10
0a5fdc3
Compare
Choose a tag to compare

The 2.2 release contains a number of bugfixes and improvements thanks to the many students who contributed as part of our Google Summer of Code selection process. Congratulations to @BreadGenie, @imsahil007 and @peb-peb who will be continuing to work with us for the next few months!

New feature highlights:

  • CVE Binary Tool can now be used to get lists of vulnerabilities affecting a python requirements.txt file, as well as lists of packages installed on .deb or .rpm based systems (Thanks to @BreadGenie)
  • Scan reports can now be merged (Thanks to @imsahil007)
  • Reports can now be generated in PDF format (Thanks to @anthonyharrison)
  • A new helper script is available to help new contributors find appropriate patterns for new checkers (Thanks to @peb-peb)
  • Reports can now be generated even if no CVEs are found (Thanks to @BreadGenie)
  • We've added rate limiting for our NVD requests (Thanks to @nisamson, @param211, @bhargavh)

There are also a number of new checkers and bug fixes.

Thanks also to @jerinjtitus, @Molkree, @alt-glitch, @CabTheProgrammer, @Romi-776, @chaitanyamogal, @Rahul2044, @utkarsh147-del , @SinghHrmn, @SaurabhK122, @pdxjohnny and @terriko for their contributions to this release.

CVE Binary Tool 2.1.post1

27 Apr 21:33
Compare
Choose a tag to compare

Rate limiting temporary fix in response to NVD API update

CVE Binary Tool 2.1

08 Dec 01:45
3e30fcf
Compare
Choose a tag to compare

This release fixes an issue with jinja2 autoescape breaking the HTML reports and includes some updates to tests.

CVE Binary Tool 2.0

12 Nov 20:33
3d09b65
Compare
Choose a tag to compare

Release date: 12 Nov 2020

This release features code from our three successful Google Summer of Code students!

Thanks also to the mentors who worked with our students this year: @terriko, @pdxjohnny, @meflin, @mdwood-intel and unofficial mentor @anthonyharrison who helped us considerably with real-world feedback.

This release also includes contributions from the following new contributors:

CVE Binary Tool 1.1.1

09 Nov 21:51
Compare
Choose a tag to compare

This point release includes fixes so documentation will build and display correctly on readthedocs. There are no functional changes to the code.

2.0 alpha release

29 Oct 07:27
2a40446
Compare
Choose a tag to compare
2.0 alpha release Pre-release
Pre-release

This is an alpha release for people interested in trying out an early preview of 2.0. Major features include performance improvements, triage options, new output modes, and many new checkers thanks to our Google Summer of Code students @Niraj-Kamdar, @SinghHrmn and @SaurabhK122 . Thanks for an incredibly productive summer!

We are expecting to make some documentation improvements before the final release, which we hope to have out next week.