Use EPSS scores to prioritize NPM Audit findings
npm install npm-epss-auditCurrently NPM Audit reports severity of vulnerabilities based on the CVSS score. Also the response received from NPM bulk audit used within npm audit do not include CVEs in the report as of May 2023. This interim tool uses the NPM Quick Audit end point to retrieve associated CVEs and reports corresponding EPSS scores to help prioritize vulnerabilities.
> Note
> Version 0.0.12+ includes support to check if a CVE is included in the CISA Known Exploited Vulnerability (KEV) catalog.
EPSS stands for Exploit Prediction Scoring System. It is a machine learning-based model that predicts the likelihood of a software vulnerability being exploited in the wild. The EPSS score is a number between 0 and 1, with a higher score indicating a higher likelihood of exploitation. The EPSS score is calculated using a variety of factors, including the severity of the vulnerability, the availability of exploit code, and the number of known attacks.
See EPSS at https://www.first.org/epss.
> For the benefit of the cybersecurity community and network defenders—and to help every organization better manage vulnerabilities and keep pace with threat activity—CISA maintains the authoritative source of vulnerabilities that have been exploited in the wild: the Known Exploited Vulnerability (KEV) catalog. CISA strongly recommends all organizations review and monitor the KEV catalog and prioritize remediation of the listed vulnerabilities to reduce the likelihood of compromise by known threat actors. All federal civilian executive branch (FCEB) agencies are required to remediate vulnerabilities in the KEV catalog within prescribed timeframes.
See CISA KEV Catalog at https://www.cisa.gov/known-exploited-vulnerabilities.
> Warning
> The CISA KEV catalog is very limited when it comes to individual NPM packages. This is included to support future use cases of the tool.
NPM Audit requires that all project dependencies are already installed and package-lock.json file exists.
Make sure to install dependencies in the project before running the tool.
``bash`Run the tool in the project directory
npx npm-epss-audit@latest
`bashInstall the tool globally
npm install -g npm-epss-audit@latest
$3
bash
Usage: npm-epss-audit [-v|--verbose] [-r|--refresh] [-f|--fail-on-past-duedate] [-t|--threshold]Options:
--version Show version number [boolean]
-v, --verbose Verbose output
-r, --refresh Refresh EPSS scores
-f, --fail-on-past-duedate Fail on past CISA KVE due date
-t, --threshold EPSS score threshold to fail the audit
[number] [default: 0]
--help Show help [boolean]
`$3
For use in CI pipelines and automation tools, the tool will exit with the following exit codes:
- 0: Ran successfully and no vulnerabilities found
- 1: Failed to run due to errors or other configuration issues
- 2: Ran successfully and vulnerabilities found that exceeded the EPSS Score threshold (default: 0.0, means all vulnerabilities are reported)
You may also use the
option to fail the audit if any of the vulnerabilities are past the CISA KEV due date or
set the --threshold option to a value of your choice greater than 0.0 to fail the audit if any of the vulnerabilities exceed the EPSS Score threshold.$3
`bash
Run with default options
npm-epss-auditAuditing v0.1.0
┌─────────┬────────────────────────┬────────────┬──────────────────┬──────┬────────────────┬───────────┬──────────┐
│ (index) │ Module │ Severity │ CVE ID │ CVSS │ EPSS Score (%) │ CISA KEV? │ Due Date │
├─────────┼────────────────────────┼────────────┼──────────────────┼──────┼────────────────┼───────────┼──────────┤
│ 0 │ 'json5' │ 'high' │ 'CVE-2022-46175' │ 7.1 │ 0.225 │ 'No' │ '' │
│ 1 │ 'loader-utils' │ 'critical' │ 'CVE-2022-37601' │ 9.8 │ 0.163 │ 'No' │ '' │
└─────────┴────────────────────────┴────────────┴──────────────────┴──────┴────────────────┴───────────┴──────────┘
Fail audit only for vulnerabilities with EPSS score greater than 0.0015 (0.15%)
npm-epss-audit --threshold 0.0015Auditing v0.1.0
┌─────────┬────────────────────────┬────────────┬──────────────────┬──────┬────────────────┬───────────┬──────────┐
│ (index) │ Module │ Severity │ CVE ID │ CVSS │ EPSS Score (%) │ CISA KEV? │ Due Date │
├─────────┼────────────────────────┼────────────┼──────────────────┼──────┼────────────────┼───────────┼──────────┤
│ 0 │ 'json5' │ 'high' │ 'CVE-2022-46175' │ 7.1 │ 0.225 │ 'No' │ '' │
│ 1 │ 'loader-utils' │ 'critical' │ 'CVE-2022-37601' │ 9.8 │ 0.163 │ 'No' │ '' │
└─────────┴────────────────────────┴────────────┴──────────────────┴──────┴────────────────┴───────────┴──────────┘
At least one CVE with EPSS Score threshold 0.0015 exceeded.
`$3
On first run, the tool will create a folder named .epss in the ${HOME} or "/tmp" folder. This folder will contain the raw EPSS Data file and uncompressed CSV file.
If you would like to choose a different folder, you may set the
This tool addresses a gap to take advantage of EPSS Scores for NPM packages, as a starting point to prioritize vulnerabilities.
This is probably just be an interim tool until NPM Audit includes CVEs and EPSS scores in the bulk audit response and audit report and
streamline this process for developers.
If you would like to contribute to this project, feel free to fork and create PR if you can.
Otherwise, create an issue with your thoughts and ideas.