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

Work on CAMEL-27328 started by Claus Ibsen.
-------------------------------------------
> camel-jbang - CVE Audit screen shows the version that fixes each artifact, 
> Camel advisories and the dependency chain
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-27328
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27328
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> The CVE Audit screen of camel-jbang scans the classpath of a running 
> integration against OSV.dev. It lists the problems, but does not say well 
> what to do about them:
> # *Fixed in* mixes the fixed versions of every package and range of an 
> advisory (e.g. 2.12.7.1, 2.13.4, 2.14.0, 2.15.0 for one jackson-databind 
> CVE). Show the nearest fixed version above the installed one, for that 
> artifact.
> # The Apache Camel security advisories that ship with the camel-catalog are 
> not used. They say which Camel release fixes a CVE of a Camel component; OSV 
> does not know which Camel release brings a fixed third-party library.
> # *Via* resolves only one level (the POMs of the direct dependencies). Show 
> the dependency chain, e.g. camel-kafka -> kafka-clients -> snappy-java.
> # Show the CVSS base score next to the severity, not only the vector.
> # A view grouped by artifact: one row per vulnerable JAR, with the number of 
> CVEs, the worst severity and the version that fixes them all (what to 
> upgrade).
> # A / filter.
> # Mark whether the routes use the component that brings the vulnerable 
> artifact in (as the MCP dependency check does).
> # Explain with AI (Shift+F8) gives the AI the exact fix (the version to pin 
> with camel.jbang.dependencies, or the Camel release with the fix), so it can 
> offer that change for the user to confirm.
> _Claude Code on behalf of Claus Ibsen_



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

Reply via email to