Claus Ibsen created CAMEL-27345:
-----------------------------------

             Summary: camel-maven-plugin - camel:audit goal checks the project 
dependencies for CVEs in CI/CD and can fail the build
                 Key: CAMEL-27345
                 URL: https://issues.apache.org/jira/browse/CAMEL-27345
             Project: Camel
          Issue Type: New Feature
          Components: tooling
            Reporter: Claus Ibsen
             Fix For: 4.24.0


Add a goal to camel-maven-plugin, e.g. {{camel:audit}}, so users can check a 
Maven project for known vulnerabilities (CVEs) in CI/CD, and report or fail the 
build. Same checks as {{camel dependency audit}} (CAMEL-27340): OSV.dev, and 
the Apache Camel security advisories of the catalog.

A generic "fail on CVE" is covered by other tools (OWASP dependency-check, 
osv-scanner, Trivy, ...). The goal adds the Camel specific parts:
* the Apache Camel security advisories, with the components the routes actually 
use (USED)
* the fix hint names the Camel version to upgrade to, not only a transitive 
override
* the VIA chain

h4. Proposal
* The dependencies come from the resolved Maven dependency graph (after BOM / 
dependencyManagement, e.g. Spring Boot or Quarkus), not from a separate 
resolution.
* Proxy from the Maven settings (active proxy with username, password, 
nonProxyHosts).
* Parameters: {{failOn}} (severity, default none = report only), 
{{failOnError}} (OSV.dev not reachable: warn or fail), {{skip}}, {{offline}} / 
the offline OSV database (separate JIRA), excluded groupIds (internal artifacts 
are not sent to OSV.dev).
* A suppression file of accepted CVE ids, each with a reason, so a team does 
not disable the whole check for one CVE that does not apply.
* Reports: console, JSON (same shape as {{camel dependency audit --json}}), 
SARIF for GitHub code scanning.
* Stale advisories: the Camel advisories ship with the catalog, so an older 
plugin only knows the advisories up to its release. Either resolve the latest 
camel-catalog through the Maven resolver (goes through the company's repository 
manager and proxy), or document to use the latest plugin version whatever the 
Camel version of the project.

Depends on the shared CVE module (separate JIRA). Docs: the camel-maven-plugin 
page, and the {{camel dependency audit}} page points to it.

_Claude Code on behalf of Claus Ibsen (davsclaus)_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to