vulnxscan is a command line utility that demonstrates running vulnerability scans using SBOM as input. It mainly targets nix packages, however, it can be used with any other targets too as long as the target is expressed as valid CycloneDX SBOM.
- Getting Started
- Example Target
- Supported Scanners
- Vulnxscan Usage Examples
- Footnotes and Future Work
To get started, follow the Getting Started section from the main README.
As an example, to run the vulnxscan from your local clone of the tiiuae/sbomnix repository:
# '--' signifies the end of argument list for `nix`.
# '--help' is the first argument to `vulnxscan`
$ nix run .#vulnxscan -- --helpIn the below examples, we use git as an example target for vulnxscan.
To print git drv-path on your local system, try:
$ nix eval -f '<nixpkgs>' 'git.drvPath'
"/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv"OSV is a vulnerability database for open-source projects initiated by Google.
OSV database currently does not support Nix ecosystem, so queries that specify Nix as ecosystem would not return any matches. For this reason vulnxscan currently does not use Google's official OSV-Scanner front-end, but implements it's own OSV client demo in osv.py.
osv.py sends queries to OSV API without specifying the ecosystem, only the target package name and version. At the time of writing, such queries to OSV API return vulnerabilities that match the given package and version across all ecosystems. As a result, the OSV vulnerabilities for Nix ecosystem will include false positives.
Also, it is worth mentioning that OSV queries without ecosystem are undocumented in the API specification currently.
Grype is a vulnerability scanner targeted for container images. It uses the vulnerability data from variety of publicly available data sources. Grype also supports input from CycloneDX SBOM which makes it possible to use Grype with SBOM input from sbomnix, thus, allowing Grype scans against Nix targets.
Vulnix is a vulnerability scanner intended for Nix targets. It uses NIST NVD vulnerability database.
Vulnix matches vulnerabilities based on heuristic, which might result more false positives compared to direct match. False positives due to rough heuristic are an intended feature in vulnix. On the other hand, vulnix accounts CVE patches applied on Nix packages when matching vulnerabilities, something currently not directly supported by other scanners.
This example shows how to use vulnxscan to summarize vulnerabilities impacting the given target or any of its runtime dependencies.
# Target can be specified with flakeref too, e.g.:
# vulnxscan .
# vulnxscan github:tiiuae/sbomnix
# vulnxscan nixpkgs#git
# Ref: https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#flake-references
$ vulnxscan /nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv
INFO Generating SBOM for target '/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv'
INFO Loading runtime dependencies referenced by '/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv'
INFO Using cdx SBOM '/tmp/vulnxscan_nmpi4h8_.json'
INFO Using csv SBOM '/tmp/vulnxscan_9vuvdabq.csv'
INFO Running vulnix scan
INFO Running grype scan
INFO Running OSV scan
INFO Querying vulnerabilities
INFO Filtering patched vulnerabilities
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO Console report
Potential vulnerabilities impacting '/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv' or some of its runtime dependencies:
| vuln_id | url | package | version | severity | grype | osv | vulnix | sum |
|------------------+---------------------------------------------------+-----------+---------+----------+-------+-----+--------+-----|
| CVE-2023-3817 | https://nvd.nist.gov/vuln/detail/CVE-2023-3817 | openssl | 3.0.9 | 5.3 | 1 | 0 | 1 | 2 |
| CVE-2022-38663 | https://nvd.nist.gov/vuln/detail/CVE-2022-38663 | git | 2.41.0 | 6.5 | 0 | 0 | 1 | 1 |
| CVE-2022-36884 | https://nvd.nist.gov/vuln/detail/CVE-2022-36884 | git | 2.41.0 | 5.3 | 0 | 0 | 1 | 1 |
| CVE-2022-36883 | https://nvd.nist.gov/vuln/detail/CVE-2022-36883 | git | 2.41.0 | 7.5 | 0 | 0 | 1 | 1 |
| CVE-2022-36882 | https://nvd.nist.gov/vuln/detail/CVE-2022-36882 | git | 2.41.0 | 8.8 | 0 | 0 | 1 | 1 |
| CVE-2022-30949 | https://nvd.nist.gov/vuln/detail/CVE-2022-30949 | git | 2.41.0 | 5.3 | 0 | 0 | 1 | 1 |
| CVE-2022-30948 | https://nvd.nist.gov/vuln/detail/CVE-2022-30948 | git | 2.41.0 | 7.5 | 0 | 0 | 1 | 1 |
| CVE-2022-30947 | https://nvd.nist.gov/vuln/detail/CVE-2022-30947 | git | 2.41.0 | 7.5 | 0 | 0 | 1 | 1 |
| MAL-2022-4301 | https://osv.dev/MAL-2022-4301 | libidn2 | 2.3.4 | | 0 | 1 | 0 | 1 |
| CVE-2021-21684 | https://nvd.nist.gov/vuln/detail/CVE-2021-21684 | git | 2.41.0 | 6.1 | 0 | 0 | 1 | 1 |
| CVE-2020-2136 | https://nvd.nist.gov/vuln/detail/CVE-2020-2136 | git | 2.41.0 | 5.4 | 0 | 0 | 1 | 1 |
| CVE-2019-1003010 | https://nvd.nist.gov/vuln/detail/CVE-2019-1003010 | git | 2.41.0 | 4.3 | 0 | 0 | 1 | 1 |
| CVE-2018-1000182 | https://nvd.nist.gov/vuln/detail/CVE-2018-1000182 | git | 2.41.0 | 6.4 | 0 | 0 | 1 | 1 |
| CVE-2018-1000110 | https://nvd.nist.gov/vuln/detail/CVE-2018-1000110 | git | 2.41.0 | 5.3 | 0 | 0 | 1 | 1 |
| CVE-2016-2781 | https://nvd.nist.gov/vuln/detail/CVE-2016-2781 | coreutils | 9.3 | 6.5 | 1 | 0 | 0 | 1 |
INFO Wrote: vulns.csvAs printed in the console output, vulnxscan first creates an SBOM, then feeds the SBOM (or target path) as input to different vulnerability scanners: vulnix, grype, and osv.py and creates a summary report. The summary report lists the newest vulnerabilities on top, with the sum column indicating how many scanners agreed with the exact same finding. In addition to the console output, vulnxscan writes the report to csv-file vulns.csv to allow easier post-processing of the output.
It is worth mentioning that vulnxscan filters out vulnerabilities that it detects are patched, as printed out in the console output on lines like 'CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']'.
This patch auto-detection works in the similar way as the patch auto-detection on vulnix, that is, it is based on detecting vulnerability identifiers from the patch filenames.
vulnxscan supports whitelisting vulnerabilities to exclude false positives, unfixable issues, or vulnerabilities known to be addressed. Whitelist is a csv file that contains rules for the vulnerabilities to be excluded from the vulnxscan console report. Consider the following example whitelist:
$ csvlook whitelist.csv
| vuln_id | package | comment |
| -------------- | --------- | ----------------------------------------------------------------------- |
| MAL-2022-4301 | | Incorrect package: Issue refers npm libidn2, not libidn2. |
| CVE-2016-2781 | coreutils | NVD data issue: CPE entry does not correctly state the version numbers. |
| CVE-20.* | git | Incorrect package: Impacts Jenkins git plugin, not git. |
vuln_id and comment are mandatory columns. vuln_id specifies a regular expression that will be used to match the vulnerability identification (vuln_id) against that of the vulnxscan output. Vulnerabilities that match the regular expression are excluded from the vulnxscan console output. If the whitelist includes a package column, in addition to matching vuln_id, a strict match is required against the package field in vulnxscan output.
In case many rules match a vulnerability, rules on top of the whitelist are given higher priority.
To be able to verify which vulnerabilities are whitelisted, vulnxscan csv output vulns.csv includes both whitelisted and non-whitelisted vulnerabilities implied with boolean column whitelist. vulns.csv also incluces the comment section from the whitelist to be able to verify the reason for whitelisting each vulnerability. Below example shows applying the above example whitelist against the git vulnxscan output from the earlier example.
# Given the whitelist.csv contents:
$ cat whitelist.csv
"vuln_id","package","comment"
"MAL-2022-4301",,"Incorrect package: Issue refers npm libidn2, not libidn2."
"CVE-2016-2781","coreutils","NVD data issue: CPE entry does not correctly state the version numbers."
"CVE-20.* ","git","Incorrect package: Impacts Jenkins git plugin, not git."
# Apply the whitelist to git vulnxscan output
$ vulnxscan /nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv --whitelist=whitelist.csv
INFO Generating SBOM for target '/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv'
INFO Loading runtime dependencies referenced by '/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv'
INFO Using cdx SBOM '/tmp/vulnxscan_8tezlf17.json'
INFO Using csv SBOM '/tmp/vulnxscan_lcj18a88.csv'
INFO Running vulnix scan
INFO Running grype scan
INFO Running OSV scan
INFO Querying vulnerabilities
INFO Filtering patched vulnerabilities
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO Applying whitelist 'whitelist.csv'
INFO Console report
Potential vulnerabilities impacting '/nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv' or some of its runtime dependencies:
# Note: the console output now includes only non-whitelisted entries:
| vuln_id | url | package | version | severity | grype | osv | vulnix | sum |
|---------------+------------------------------------------------+-----------+---------+----------+-------+-----+--------+-----|
| CVE-2023-3817 | https://nvd.nist.gov/vuln/detail/CVE-2023-3817 | openssl | 3.0.9 | 5.3 | 1 | 0 | 1 | 2 |
INFO Wrote: vulns.csv
# In addition to the console report, vulnxscan writes a detailed report in a csv file,
# by default 'vulns.csv', which includes the full details also from the whitelisted vulnerabilities:
$ csvlook vulns.csv
| vuln_id | url | package | version | severity | grype | osv | vulnix | sum | sortcol | whitelist | whitelist_comment |
| ---------------- | ------------------------------------------------- | --------- | ------- | -------- | ----- | ----- | ------ | --- | --------------- | --------- | ----------------------------------------------------------------------- |
| CVE-2023-3817 | https://nvd.nist.gov/vuln/detail/CVE-2023-3817 | openssl | 3.0.9 | 5.3 | True | False | True | 2 | 2023A0000003817 | False | |
| CVE-2022-38663 | https://nvd.nist.gov/vuln/detail/CVE-2022-38663 | git | 2.41.0 | 6.5 | False | False | True | 1 | 2022A0000038663 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2022-36884 | https://nvd.nist.gov/vuln/detail/CVE-2022-36884 | git | 2.41.0 | 5.3 | False | False | True | 1 | 2022A0000036884 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2022-36883 | https://nvd.nist.gov/vuln/detail/CVE-2022-36883 | git | 2.41.0 | 7.5 | False | False | True | 1 | 2022A0000036883 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2022-36882 | https://nvd.nist.gov/vuln/detail/CVE-2022-36882 | git | 2.41.0 | 8.8 | False | False | True | 1 | 2022A0000036882 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2022-30949 | https://nvd.nist.gov/vuln/detail/CVE-2022-30949 | git | 2.41.0 | 5.3 | False | False | True | 1 | 2022A0000030949 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2022-30948 | https://nvd.nist.gov/vuln/detail/CVE-2022-30948 | git | 2.41.0 | 7.5 | False | False | True | 1 | 2022A0000030948 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2022-30947 | https://nvd.nist.gov/vuln/detail/CVE-2022-30947 | git | 2.41.0 | 7.5 | False | False | True | 1 | 2022A0000030947 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| MAL-2022-4301 | https://osv.dev/MAL-2022-4301 | libidn2 | 2.3.4 | | False | True | False | 1 | 2022A0000004301 | True | Incorrect package: Issue refers npm libidn2, not libidn2. |
| CVE-2021-21684 | https://nvd.nist.gov/vuln/detail/CVE-2021-21684 | git | 2.41.0 | 6.1 | False | False | True | 1 | 2021A0000021684 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2020-2136 | https://nvd.nist.gov/vuln/detail/CVE-2020-2136 | git | 2.41.0 | 5.4 | False | False | True | 1 | 2020A0000002136 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2019-1003010 | https://nvd.nist.gov/vuln/detail/CVE-2019-1003010 | git | 2.41.0 | 4.3 | False | False | True | 1 | 2019A0001003010 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2018-1000182 | https://nvd.nist.gov/vuln/detail/CVE-2018-1000182 | git | 2.41.0 | 6.4 | False | False | True | 1 | 2018A0001000182 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2018-1000110 | https://nvd.nist.gov/vuln/detail/CVE-2018-1000110 | git | 2.41.0 | 5.3 | False | False | True | 1 | 2018A0001000110 | True | Incorrect package: Impacts Jenkins git plugin, not git. |
| CVE-2016-2781 | https://nvd.nist.gov/vuln/detail/CVE-2016-2781 | coreutils | 9.3 | 6.5 | True | False | False | 1 | 2016A0000002781 | True | NVD data issue: CPE entry does not correctly state the version numbers. |See ghafscan manual_analysis.csv for a more complete example and usage of the vulnxscan whitelisting feature.
This example shows how to use vulnxscan to summarize vulnerabilities impacting components in the given CycloneDX SBOM.
First, we use sbomnix to generate SBOM for the example target:
$ nix run .#sbomnix /nix/store/ay9sn71cssl4wd7s6bd8xah0zcwqiq2q-git-2.41.0.drv
..
INFO Wrote: sbom.cdx.jsonThen, give the generated SBOM as input to vulnxscan:
$ vulnxscan --sbom sbom.cdx.json
INFO Running grype scan
INFO Running OSV scan
INFO Querying vulnerabilities
INFO Console report
Potential vulnerabilities impacting components in 'sbom.cdx.json':
| vuln_id | url | package | version | severity | grype | osv | sum |
|---------------+------------------------------------------------+-----------+---------+----------+-------+-----+-----|
| CVE-2023-3817 | https://nvd.nist.gov/vuln/detail/CVE-2023-3817 | openssl | 3.0.9 | 5.3 | 1 | 0 | 1 |
| CVE-2023-2975 | https://nvd.nist.gov/vuln/detail/CVE-2023-2975 | openssl | 3.0.9 | 5.3 | 1 | 0 | 1 |
| MAL-2022-4301 | https://osv.dev/MAL-2022-4301 | libidn2 | 2.3.4 | | 0 | 1 | 1 |
| CVE-2016-2781 | https://nvd.nist.gov/vuln/detail/CVE-2016-2781 | coreutils | 9.3 | 6.5 | 1 | 0 | 1 |
INFO Wrote: vulns.csvNotice that vulnxscan drops the vulnix scan when the input is SBOM. This is due to the vulnix not supporting SBOM input at the time of writing.
Also notice that vulnxscan drops the patch auto-detection if the input is SBOM. Reason is that vulnxscan reads the patch information from nix derivations. Therefore, the patch information is only available when the given input is Nix store path (e.g. derivation or out-path), not SBOM.
By default, vulnxscan scans the given target for vulnerabilities that impact its runtime-only dependencies. This example shows how to use vulnxscan to include also buildtime dependencies to the scan.
$ vulnxscan ./result --buildtime
# ... output not included in this snippet ... vulnxscan supports using whitelist csv file as a more generic record of manual analysis results, by allowing non-whitelisting rules. That is, the whitelist csv file can include a boolean whitelist column to indicate if the matching vulnerabilities should be whitelisted or not. The default value for whitelist is True, that is, if the whitelist column is missing or the value is empty, vulnxscan interprets the rule as if the whitelist column value would evaluate to True.
As an example, consider the following manual analysis record (i.e. 'whitelist'):
csvlook manual_analysis.csv
| vuln_id | whitelist | package | comment |
| -------------- | --------- | --------- | ------------------------------------------------------------------ |
| CVE-2022-0856 | False | libcaca | Not fixed upstream: https://github.com/cacalabs/libcaca/issues/65. |
| CVE-2021-32490 | False | djvulibre | Pending merge: https://github.com/NixOS/nixpkgs/pull/246773. |
The above example manual_analysis.csv includes two rules: one for CVE-2022-0856 and one for CVE-2021-32490. For both, the whitelist column value is 'False', indicating the rule is a non-whitelisting rule. This means, for both cases, we want to record the manual analysis results as detailed in the comment column, but we don't want to whitelist the matching vulnerabilities. Specifically, in the case of CVE-2022-0856 we don't want to whitelist the issue since it's not fixed upstream, but we still want to record the link to the upstream PR to make it easier to follow the upstream progress. In the case of CVE-2021-32490 we don't want to whitelist the issue since the nixpkgs PR is pending merge. In this case too, we still want to record the nixpkgs PR to allow following the progress.
See ghafscan manual_analysis.csv for a more complete example and usage of non-whitelisting rules to help manual analysis.
vulnxscan can be used to help manual analysis with --triage and --nixprs command line options.
With command line option --triage, vulnxscan queries repology.org for nix-unstable and package upstream version information, as well as the CVE impacted versions. With the additional information from repology.org, vulnxscan classifies each vulnerability accordingly.
Consider the following example, using ghaf as target:
# In devshell
# Get the target drv path for a specific flake target:
$ nix eval github:tiiuae/ghaf?ref=main#packages.x86_64-linux.generic-x86_64-release.drvPath
"/nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv"
# Run vulnxscan:
# --buildtime: Scan buildtime dependencies. Scanning buildtime dependencies does not
# require building the target, which allows relatively quick scan also for
# targets not built earlier. Notice: nix 'buildtime' dependencies are a
# superset of runtime dependencies.
# --whitelist: Use 'manual_analysis.csv' as a whitelist file.
# --triage : Help manual analysis by querying version info from repology.org.
$ vulnxscan /nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv --buildtime --whitelist=manual_analysis.csv --triage
INFO Generating SBOM for target '/nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv'
INFO Loading buildtime dependencies referenced by '/nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv'
INFO Using cdx SBOM '/tmp/vulnxscan_wt98z5yu.json'
INFO Using csv SBOM '/tmp/vulnxscan_9ijk42ar.csv'
INFO Running vulnix scan
INFO Running grype scan
INFO Running OSV scan
INFO Querying vulnerabilities
INFO Filtering patched vulnerabilities
INFO CVE-2023-27371 for 'libmicrohttpd' is patched with: ['/nix/store/l53sq07v6hghm7cchcjbrwyvjyjag06r-CVE-2023-27371.patch']
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO CVE-2023-2975 for 'openssl' is patched with: ['/nix/store/7gz0nj14469r9dlh8p0j5w5wjj3b6hw4-CVE-2023-2975.patch']
INFO CVE-2023-2617 for 'opencv' is patched with: ['/nix/store/vw29nr5nrfs10vv5p3m7rpkqscwrh4sp-CVE-2023-2617.patch']
...
Potential vulnerabilities impacting version_local:
| vuln_id | package | severity | version_local | version_nixpkgs | version_upstream | classify |
|---------------------+------------+----------+---------------+-----------------+------------------+--------------------------------------|
| CVE-2023-40360 | qemu | 5.5 | 8.0.2 | 8.1.0 | 8.1.0 | fix_update_to_version_nixpkgs |
| CVE-2023-40359 | xterm | 9.8 | 379 | 384 | 384 | fix_update_to_version_nixpkgs |
| CVE-2023-39742 | giflib | 5.5 | 5.2.1 | 5.2.1 | 5.2.1 | fix_not_available |
| CVE-2023-39533 | go | 7.5 | 1.20.6 | 1.21.1 | 1.21.1 | fix_update_to_version_nixpkgs |
| CVE-2023-38858 | faad2 | 6.5 | 2.10.1 | 2.10.1 | 2.10.1 | fix_not_available |
| CVE-2023-38857 | faad2 | 5.5 | 2.10.1 | 2.10.1 | 2.10.1 | fix_not_available |
| CVE-2023-38633 | librsvg | 5.5 | 2.55.1 | 2.56.3 | 2.56.3 | fix_update_to_version_nixpkgs |
| CVE-2023-37769 | pixman | 6.5 | 0.42.2 | 0.42.2 | 0.42.2 | err_not_vulnerable_based_on_repology |
| CVE-2023-31484 | perl | 8.1 | 5.36.0-env | 5.38.0 | 5.38.0 | fix_update_to_version_nixpkgs |
| CVE-2023-31484 | perl | 8.1 | 5.36.0 | 5.38.0 | 5.38.0 | fix_update_to_version_nixpkgs |
| CVE-2023-30571 | libarchive | 5.3 | 3.6.2 | 3.6.2 | 3.7.1 | fix_update_to_version_upstream |
| CVE-2023-29409 | go | 5.3 | 1.20.6 | 1.21.1 | 1.21.1 | fix_update_to_version_nixpkgs |
| CVE-2023-29383 | shadow | 3.3 | 4.13 | 4.13 | 4.14.0 | fix_update_to_version_upstream |
... (output truncated) ...
INFO Wrote: /home/hrosten/projects/sbomnix-fork/vulns.csv
INFO Wrote: /home/hrosten/projects/sbomnix-fork/vulns.triage.csvAs an example, the output table states the following:
- Package
qemu8.0.2, which is a dependency to ghaf, is potentially vulnerable to CVE-2023-40360. - Based on repology.org,
qemunewest version in nix-unstable is 8.0.4. Also, based on repology.org, latestqemuversion in theqemuupstream is 8.1.0. - Since both
qemu8.0.2 and 8.0.4 are vulnerable to CVE-2023-40360, but the upstream version 8.1.0 is not vulnerable,vulnxscanclassifies the issue asfix_update_to_version_upstream. - Package
xtermversion 379 is potentially vulnerable to CVE-2023-40359. Latest version ofxtermin nix-unstable is 384, which is not vulnerable to CVE-2023-40359. Therefore,vulnxscanclassifies the issue asfix_update_to_version_nixpkgs. - Package
giflibversion 5.2.1 is potentially vulnerable to CVE-2023-39742. Since there's no known fixed version available in nix-unstable or the package upstream,vulnxscanclassifies the issue asfix_not_available. Notice that the classification is based only on the version numbers. Indeed, it's still possible that there's an upstream patch available in an unreleased version ofgiflibthat would fix the issue. - Package
pixmanversion 0.42.2 is potentially vulnerable to CVE-2023-37769. However, based on repology.org, the vulnerability does not impact the given version ofpixman. Therefore,vulnxscanclassifies the issue aserr_not_vulnerable_based_on_repology.
With command line option --nixprs, vulnxscan queries github for nixpkgs PRs that might include more information concerning possible nixpkgs fixes for the found vulnerabilities. --nixprs adds URLs to (at most five) PRs that appear valid for each vulnerability based on heuristic. The PR search takes significant time due to github API rate limits, which is why it is not enabled by default.
Consider the following example, using the same Ghaf target as earlier:
# Run vulnscan with --triage and --nixprs
$ vulnxscan /nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv --buildtime --whitelist=manual_analysis.csv --triage --nixprs
INFO Generating SBOM for target '/nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv'
INFO Loading buildtime dependencies referenced by '/nix/store/5fjfirqjsxggkx4k8ylrrrjar1c54zxp-nixos-disk-image.drv'
...
Potential vulnerabilities impacting version_local:
| vuln_id | package | severity | version_local | version_nixpkgs | version_upstream | classify | nixpkgs_pr |
|----------------+------------+------------+---------------+-----------------+------------------+-------------------------------+-----------------------------------------------|
| CVE-2023-40360 | qemu | 5.5 | 8.0.2 | 8.1.0 | 8.1.0 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/251154 |
| CVE-2023-40359 | xterm | 9.8 | 379 | 384 | 384 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/244141 |
| CVE-2023-39742 | giflib | 5.5 | 5.2.1 | 5.2.1 | 5.2.1 | fix_not_available | |
| CVE-2023-39533 | go | 7.5 | 1.20.6 | 1.21.1 | 1.21.1 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/253738 |
| CVE-2023-38858 | faad2 | 6.5 | 2.10.1 | 2.10.1 | 2.10.1 | fix_not_available | |
| CVE-2023-38857 | faad2 | 5.5 | 2.10.1 | 2.10.1 | 2.10.1 | fix_not_available | |
| CVE-2023-38633 | librsvg | 5.5 | 2.55.1 | 2.56.3 | 2.56.3 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/246763 |
| | | | | | | | https://github.com/NixOS/nixpkgs/pull/246860 |
| CVE-2023-37769 | pixman | 6.5 | 0.42.2 | 0.42.2 | 0.42.2 | err_not_vulnerable_based_on_re| |
| CVE-2023-31484 | perl | 8.1 | 5.36.0-env | 5.38.0 | 5.38.0 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/241848 |
| | | | | | | | https://github.com/NixOS/nixpkgs/pull/247547 |
| CVE-2023-31484 | perl | 8.1 | 5.36.0 | 5.38.0 | 5.38.0 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/241848 |
| | | | | | | | https://github.com/NixOS/nixpkgs/pull/247547 |
| CVE-2023-30571 | libarchive | 5.3 | 3.6.2 | 3.6.2 | 3.7.1 | fix_update_to_version_upstream| |
| CVE-2023-29409 | go | 5.3 | 1.20.6 | 1.21.1 | 1.21.1 | fix_update_to_version_nixpkgs | https://github.com/NixOS/nixpkgs/pull/247034 |
| | | | | | | | https://github.com/NixOS/nixpkgs/pull/253738 |
| CVE-2023-29383 | shadow | 3.3 | 4.13 | 4.13 | 4.14.0 | fix_update_to_version_upstream| https://github.com/NixOS/nixpkgs/pull/233924 |
| | | | | | | | https://github.com/NixOS/nixpkgs/pull/254143 |vulnxscan option --nixprs adds the column nixpkgs_pr to the output, to help manual analysis by listing PRs that appear relevant for the given issue.
For now, consider vulnxscan as a demonstration. Some improvement ideas are listed below:
- Consider adding patch information to SBOM (e.g. via the pedigree attribute) to be able to auto-detect patched vulnerabilities also when the input is SBOM.
- Vulnerability scanners lack support for parsing the patch data: even if
sbomnixadded the patch data to the output SBOM, we suspect not many vulnerability scanners would read the information. As an example, the following discussion touches this topic on DependencyTrack: DependencyTrack/dependency-track#919. - Identifying packages is hard as pointed out in https://discourse.nixos.org/t/the-future-of-the-vulnerability-roundups/22424/5. As an example, CPEs are inaccurate which causes issues in matching vulnerabilities: DependencyTrack/dependency-track#2290.
- Nix ecosystem is not supported in OSV: the way
osv.pymakes use of OSV data for Nix targets -- as explained in section Nix and OSV vulnerability database -- makes the reported OSV vulnerabilities include false positives.
- vulnxscan could include more scanners in addition to vulnix, grype, and osv.py. Suggestions for other open-source scanners, especially those that can digest CycloneDX or SPDX SBOMs are welcome. Consider e.g. bombon and cve-bin-tool. Adding cve-bin-tool to vulnxscan was demonstrated earlier, but not merged due to reasons explained in the PR.