feat(ci): Expand CVE reporting to med and low

[czentgr]

Currently, only CVEs with a score about 7.0 are reported in the OWASP job. This helps getting alerted to high and critical CVEs. But even medium and low ranked CVEs have to be mitigated even if the timeline for them is longer. This helps to have the upstream project as free of CVEs as possible.

Description

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== NO RELEASE NOTE ==

Summary by Sourcery

CI:

• Lower the default CVSS threshold in the OWASP dependency-check workflow so that medium and low severity CVEs are also reported.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the OWASP dependency check GitHub Actions workflow to report all CVEs (including low and medium severity) by lowering the default CVSS threshold used in the job.

Sequence diagram for PR-triggered OWASP dependency check with expanded CVE reporting

sequenceDiagram
  actor Developer
  participant GitHub
  participant Workflow as GitHub_Workflow_owasp_dependency_check
  participant Job as OWASP_Job
  participant Scanner as OWASP_Dependency_Check

  Developer->>GitHub: Open or update pull request
  GitHub->>Workflow: Trigger owasp-dependency-check.yml
  Workflow->>Job: Start job with env resolution
  Job->>Job: Resolve CVSS_THRESHOLD
  alt Input cvss-threshold provided
    Job->>Job: CVSS_THRESHOLD = input value
  else No input provided
    Job->>Job: CVSS_THRESHOLD = 0.1
  end
  Job->>Scanner: Run scan with CVSS_THRESHOLD
  Scanner-->>Job: Detected CVEs (all severities >= threshold)
  Job-->>GitHub: Publish report including low, medium, high, critical CVEs
  GitHub-->>Developer: Show OWASP report in PR checks

Loading

Flow diagram for CVSS threshold resolution in OWASP workflow

flowchart TD
  Start["Start OWASP job"] --> CheckInput["Check github.event.inputs.cvss-threshold"]
  CheckInput -->|Present| UseInput["Set CVSS_THRESHOLD to provided input value"]
  CheckInput -->|Missing| UseDefault["Set CVSS_THRESHOLD to default 0.1"]
  UseInput --> RunScan["Run OWASP Dependency Check"]
  UseDefault --> RunScan
  RunScan --> Filter["Include CVEs with score >= CVSS_THRESHOLD"]
  Filter --> Report["Generate CI CVE report"]

Loading

File-Level Changes

Change	Details	Files
Broaden OWASP dependency-check reporting to include low and medium severity CVEs by lowering the default CVSS threshold.	Change the OWASP CI job environment variable CVSS_THRESHOLD default from 7.0 to 0.1 when no explicit cvss-threshold input is provided Retain existing support for overriding the threshold via the cvss-threshold workflow input	.github/workflows/owasp-dependency-check.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• If the intent is to include medium and low severities, consider using a threshold around 0.0 or 0.1–4.0 rather than 0.1 alone, and double-check that this aligns with OWASP’s severity ranges so you don’t inadvertently exclude some low-severity CVEs.
• Lowering the default CVSS_THRESHOLD for all runs may significantly increase noise and CI churn; consider making this stricter default apply only on main or scheduled runs, or exposing a clearer input option to toggle between high-only and all severities modes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- If the intent is to include medium and low severities, consider using a threshold around 0.0 or 0.1–4.0 rather than 0.1 alone, and double-check that this aligns with OWASP’s severity ranges so you don’t inadvertently exclude some low-severity CVEs.
- Lowering the default CVSS_THRESHOLD for all runs may significantly increase noise and CI churn; consider making this stricter default apply only on main or scheduled runs, or exposing a clearer input option to toggle between `high-only` and `all severities` modes.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}