[ 
https://issues.apache.org/jira/browse/CAMEL-27348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-27348 started by Claus Ibsen.
-------------------------------------------
> camel-jbang - CVE audit checks the Apache Camel security advisories online 
> from camel-website, with the catalog as the fallback
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-27348
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27348
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang, tooling
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> The CVE audit (camel dependency audit, the CVE Audit screen of the TUI, 
> camel-report:audit) checks the Camel JARs against the Apache Camel security 
> advisories that ship with the catalog. That copy is only as new as the 
> release, and an older CLI or plugin knows only the advisories up to its 
> release. The advisories are published in the camel-website repository 
> ({{content/security/*.md}}) as soon as they are public.
> h4. Proposal
> * Check the advisories online, from camel-website on GitHub, and merge them 
> with those of the catalog by CVE id (the online one wins); the catalog stays 
> the fallback when GitHub cannot be reached, and with {{--offline}}.
> * One GitHub API call lists {{content/security}}; only the new and changed 
> files (by their sha) are downloaded from raw.githubusercontent.com, so a 
> refresh is usually one request. Cached in {{~/.camel/advisories}}, refreshed 
> once a day; the copy of the day before is used, with a warning, when the 
> refresh fails. Through the proxy of the Maven settings or HTTPS_PROXY 
> (CAMEL-27342), and {{GITHUB_TOKEN}} when set.
> * The parser of the advisory Markdown moves from the 
> update-security-advisories goal of camel-package-maven-plugin to 
> camel-tooling-model, so the build and the audit read the advisories the same 
> way.
> * The URL can point at a mirror (a JSON file in the format of the catalog, 
> such as one kept on the repository manager of the company) or a file, for 
> machines without access to GitHub.
> * The output says which advisories were used (online, updated <date>, or the 
> catalog of <version>).
> Related: CAMEL-27347 keeps the copy of the catalog in sync before each 
> release.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_



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

Reply via email to