Merge branch 'main' into improved-sbom-filename-extension-handling

Author: Saksham-Sirohi

.github/workflows/codeql-analysis.yml

@@ -51,7 +51,7 @@ jobs:
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@b56ba49b26e50535fa1e7f7db0f4f7b4bf65d80d # v3.28.10
+      uses: github/codeql-action/init@6bb031afdd8eb862ea3fc1848194185e076637e5 # v3.28.11
       with:
         languages: ${{ matrix.language }}
         # If you wish to specify custom queries, you can do so here or in a config file.
@@ -76,4 +76,4 @@ jobs:
     #   make release
 
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@b56ba49b26e50535fa1e7f7db0f4f7b4bf65d80d # v3.28.10
+      uses: github/codeql-action/analyze@6bb031afdd8eb862ea3fc1848194185e076637e5 # v3.28.11

.github/workflows/formatting.yml

@@ -36,7 +36,7 @@ jobs:
         run: |
           python cve_bin_tool/format_checkers.py
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@dd2324fc52d5d43c699a5636bcf19fceaa70c284 # v7.0.7
+        uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           commit-message: "chore: update checkers table"
           title: "chore: update checkers table"

.github/workflows/sbom.yml

@@ -62,7 +62,7 @@ jobs:
           cp cve-bin-tool-py${{ matrix.python }}.json sbom/cve-bin-tool-py${{ matrix.python }}.json
       - name: Create Pull Request
         if: ${{ steps.diff-sbom.outputs.changed }}
-        uses: peter-evans/create-pull-request@dd2324fc52d5d43c699a5636bcf19fceaa70c284 # v7.0.7
+        uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           commit-message: "chore: update SBOM for Python ${{ matrix.python }}"
           title: "chore: update SBOM for Python ${{ matrix.python }}"

.github/workflows/scorecard.yml

@@ -27,7 +27,7 @@ jobs:
           persist-credentials: false
 
       - name: "Run analysis"
-        uses: ossf/scorecard-action@62b2cac7ed8198b15735ed49ab1e5cf35480ba46 # v2.4.0
+        uses: ossf/scorecard-action@f49aabe0b5af0936a0987cfb85d86b75731b0186 # v2.4.1
         with:
           results_file: results.sarif
           results_format: sarif

.github/workflows/update-js-dependencies.yml

@@ -54,7 +54,7 @@ jobs:
         run: python -m pytest -v -n auto test/test_html.py
 
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@dd2324fc52d5d43c699a5636bcf19fceaa70c284 # v7.0.7
+        uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           commit-message: "chore: update js dependencies"
           title: "chore: update js dependencies"

.github/workflows/update-pre-commit.yml

@@ -48,7 +48,7 @@ jobs:
           python .github/workflows/update-dev-requirements.py
 
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@dd2324fc52d5d43c699a5636bcf19fceaa70c284 # v7.0.7
+        uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           commit-message: "chore: update pre-commit config"
           title: "chore: update pre-commit config"

.github/workflows/update-spdx-header.yml

@@ -33,7 +33,7 @@ jobs:
           sed -i "s/[0-9]\{4\}/$(date +%Y)/" spdx_header.txt
 
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@dd2324fc52d5d43c699a5636bcf19fceaa70c284 # v7.0.7
+        uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           commit-message: 'chore: update spdx header'
           title: 'chore: update spdx header'

README.md

@@ -75,7 +75,7 @@ If you want to try the latest code from
 
 Pip will install the python requirements for you, but for some types of extraction we use system libraries. If you have difficulties extracting files, you may want to look at our [additional Requirements lists for Linux and Windows](#additional-requirements).
 
-On first usage (and by default, once per day) The tool will download vulnerability data from [a set of known vulnerability data sources](https://github.com/intel/cve-bin-tool/blob/main/doc/MANUAL.md#data-sources).  Due to reliability issues with NVD, as of release 3.3 we will be using our own NVD mirror at [https://cveb.in/](https://cveb.in/) by default rather than contacting NVD directly.  If you wish to get data directly from the NVD servers you must [provide your own NVD_API_KEY](https://github.com/intel/cve-bin-tool/blob/main/doc/MANUAL.md#--nvd-api-key-nvd_api_key) to use their API.
+On first usage (and by default, once per day), the tool will download vulnerability data from [a set of known vulnerability data sources](https://github.com/intel/cve-bin-tool/blob/main/doc/MANUAL.md#data-sources).  Due to reliability issues with NVD, as of release 3.3, we will be using our own NVD mirror at [https://cveb.in/](https://cveb.in/) by default rather than contacting NVD directly.  If you wish to get data directly from the NVD servers, you must [provide your own NVD_API_KEY](https://github.com/intel/cve-bin-tool/blob/main/doc/MANUAL.md#--nvd-api-key-nvd_api_key) to use their API.
 
 If you are using a release prior to 3.3 that does not use our mirror, please use an NVD_API_KEY as described above.
 
@@ -123,7 +123,7 @@ The [SBOM generation how-to guide](https://github.com/intel/cve-bin-tool/blob/ma
 
 ### Generating a VEX
 
-As well as scanning VEX, CVE Binary Tool can be used to generate an VEX from a scan as follows:
+As well as scanning VEX, CVE Binary Tool can be used to generate a VEX from a scan as follows:
 
 ```bash
 cve-bin-tool  --vex-type <vex_type> --vex-output <vex_filename> <other scan options as required>
@@ -137,7 +137,7 @@ The [VEX generation how-to guide](https://github.com/intel/cve-bin-tool/blob/mai
 ### Triaging vulnerabilities
 
 The `--vex-file` option can be used to add extra triage data like remarks, comments etc. while scanning a directory so that output will reflect this triage data and you can save time of re-triaging (Usage: `cve-bin-tool --vex-file test.json /path/to/scan`).
-The supported format is the [CycloneDX](https://cyclonedx.org/capabilities/vex/),[CSAF](https://oasis-open.github.io/csaf-documentation/) and [OpenVEX](https://edu.chainguard.dev/open-source/sbom/what-is-openvex/) VEX format which can be generated using the `--vex-output` option.
+The supported formats are the [CycloneDX](https://cyclonedx.org/capabilities/vex/), [CSAF](https://oasis-open.github.io/csaf-documentation/) and [OpenVEX](https://edu.chainguard.dev/open-source/sbom/what-is-openvex/) VEX formats which can be generated using the `--vex-output` option.
 
 Typical usage:
 
@@ -385,7 +385,7 @@ The tool does not guarantee that any vulnerabilities reported are actually prese
 
 Users can add triage information to reports to mark issues as false positives, indicate that the risk has been mitigated by configuration/usage changes, and so on.
 
-Triage details can be re-used on other projects so, for example, triage on a Linux base image could be applied to multiple containers using that image.
+Triage details can be reused on other projects so, for example, triage on a Linux base image could be applied to multiple containers using that image.
 
 For more information and usage of triage information with the tool kindly have a look [here](https://cve-bin-tool.readthedocs.io/en/latest/triaging_process.html).
 
@@ -508,6 +508,7 @@ Output:
                         specify type of software bill of materials (sbom) to generate (default: spdx)
   <a href="https://github.com/intel/cve-bin-tool/blob/main/doc/MANUAL.md#--sbom-format">--sbom-format {tag,json,yaml}</a>
                         specify format of software bill of materials (sbom) to generate (default: tag)
+  --strip-scan-dir      strip scan directory from sbom evidence location paths and CVE paths (useful with a firmware dump)
 
 Vex Output:
   Arguments related to Vex output document.

cve_bin_tool/checkers/README.md

@@ -35,7 +35,7 @@ from cve_bin_tool.checkers import Checker
 class CurlChecker(Checker):
 ```
 
-Every checker may contain following 5 class attributes specific to product(ex: curl)
+Every checker may contain following 5 class attributes specific to product (ex: curl)
 you are making checker for:
 
 1. CONTAINS_PATTERNS - list of commonly found strings in the binary of the product
@@ -45,7 +45,7 @@ you are making checker for:
 NVD.
 5. IGNORE_PATTERNS (optional) - list of patterns that could cause false positives (e.g. error messages that mention specific product/versions)
 
-`CONTAINS_PATTERN`, `FILENAME_PATTERNS` and `VERSION_PATTERNS` supports regex to cover
+`CONTAINS_PATTERN`, `FILENAME_PATTERNS`, `VERSION_PATTERNS` and `IGNORE_PATTERNS` supports regex to cover
 wide range of use cases.
 
 Once the checker is added, its name should also be added to `__init__.py` (so

cve_bin_tool/cli.py

@@ -348,9 +348,9 @@ def main(argv=None):
         help="specify format of software bill of materials (sbom) to generate (default: tag)",
     )
     output_group.add_argument(
-        "--sbom-strip-root",
+        "--strip-scan-dir",
         action="store_true",
-        help="strip SBOM root from evidence location paths (useful when building SBOM from firmware dump)",
+        help="strip scan directory from sbom evidence location paths and CVE paths (useful with a firmware dump)",
         default=False,
     )
     vex_output_group = parser.add_argument_group(
@@ -1250,7 +1250,7 @@ def main(argv=None):
             sbom_type=args["sbom_type"],
             sbom_format=args["sbom_format"],
             sbom_root=sbom_root,
-            sbom_strip_root=args["sbom_strip_root"],
+            strip_scan_dir=args["strip_scan_dir"],
             offline=args["offline"],
         )