vulnlist 0.22.0

vulnlist ~= 'vulnerability data funnel'

vulnlist

A tool for fetching, transforming, and storing vulnerability data from a variety of sources.

Supported data sources:

• Alpine (https://secdb.alpinelinux.org)
• Amazon (https://alas.aws.amazon.com/AL2/alas.rss & https://alas.aws.amazon.com/AL2022/alas.rss)
• Debian (https://security-tracker.debian.org/tracker/data/json & https://salsa.debian.org/security-tracker-team/security-tracker/raw/master/data/DSA/list)
• GitHub Security Advisories (https://api.github.com/graphql)
• NVD (https://services.nvd.nist.gov/rest/json/cves/2.0)
• Oracle (https://linux.oracle.com/security/oval)
• RedHat (https://www.redhat.com/security/data/oval)
• SLES (https://ftp.suse.com/pub/projects/security/oval)
• Ubuntu (https://launchpad.net/ubuntu-cve-tracker)
• Wolfi (https://packages.wolfi.dev)

Installation

With pip:

pip install vulnlist

With docker:

docker run \
  --rm -it \
  -v $(pwd)/data:/data \
  -v $(pwd)/.vulnlist.yaml:/.vulnlist.yaml \
    ghcr.io/khulnasoft-lab/vulnlist:latest  \
      run nvd

Where:

• the data volume keeps the processed data on the host
• the .vulnlist.yaml uses the host application config (if present)
• you can swap latest for a specific version (same as the git tags)

See the vulnlist package for a full listing of available tags.

Getting Started

List the available vulnerability data providers:

$ vulnlist list

alpine
amazon
chainguard
debian
github
mariner
nvd
oracle
rhel
sles
ubuntu
wolfi

Download and process a provider:

$ vulnlist run wolfi

2023-01-04 13:42:58 root [INFO] running wolfi provider
2023-01-04 13:42:58 wolfi [INFO] downloading Wolfi secdb https://packages.wolfi.dev/os/security.json
2023-01-04 13:42:59 wolfi [INFO] wrote 56 entries
2023-01-04 13:42:59 wolfi [INFO] recording workspace state

You will see the processed vulnerability data in the local ./data directory

$ tree data

data
└── wolfi
    ├── checksums
    ├── metadata.json
    ├── input
    │   └── secdb
    │       └── os
    │           └── security.json
    └── results
        └── wolfi:rolling
            ├── CVE-2016-2781.json
            ├── CVE-2017-8806.json
            ├── CVE-2018-1000156.json
            └── ...

Note: to get more verbose output, use -v, -vv, or -vvv (e.g. vulnlist -vv run wolfi)

Delete existing input and result data for one or more providers:

$ vulnlist clear wolfi

2023-01-04 13:48:31 root [INFO] clearing wolfi provider state

Example config file for changing application behavior:

# .vulnlist.yaml
root: ./processed-data

log:
  level: trace

providers:
  wolfi:
    request_timeout: 125
    runtime:
      existing_input: keep
      existing_results: delete-before-write
      on_error:
        action: fail
        input: keep
        results: keep
        retry_count: 3
        retry_delay: 10

Use vulnlist config to get a better idea of all of the possible configuration options.

FAQ

Can I implement a new provider?

Yes you can! See the provider docs for more information.

Why is it called "vulnlist"?

This tool "funnels" vulnerability data into a single spot for easy processing... say "vulnerability data funnel" 100x fast enough and eventually it'll slur to "vulnlist" :).