[
https://issues.apache.org/jira/browse/CAMEL-27344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-27344 started by Claus Ibsen.
-------------------------------------------
> CVE audit - offline OSV database (Maven all.zip from a configurable URL) so
> no coordinates leave the company
> ------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-27344
> URL: https://issues.apache.org/jira/browse/CAMEL-27344
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang, tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> The CVE audit sends every GAV of the project to the live OSV.dev API
> ({{https://api.osv.dev/v1/querybatch}}). For companies this has three
> problems:
> # the coordinates leave the company, including internal ones
> ({{com.acme:billing-core}}); many security teams forbid that
> # OSV.dev is a free service with no API key and no SLA, so it is a weak base
> for a CI gate
> # build machines often have no internet access at all, proxy or not
> OSV publishes a full export of each ecosystem, updated daily:
> {{https://osv-vulnerabilities.storage.googleapis.com/Maven/all.zip}} (10.5
> MB, checked 2026-11-21).
> h4. Proposal
> An offline database mode for the CVE audit (CLI, TUI, Maven goal):
> * download {{Maven/all.zip}} from a configurable URL, so it can point at the
> company's own Nexus / Artifactory proxying it, or a file on disk
> * cache it locally (e.g. under {{~/.camel}} / the local Maven repository) and
> refresh it once a day, or on demand
> * match the versions locally with the existing range code
> ({{OsvClient.extractRanges}}, {{ComparableVersion}}); OSV Maven ranges are of
> type ECOSYSTEM with Maven version ordering, and some entries list explicit
> {{versions}}
> * no coordinates leave the company, and no proxy is needed when the URL is
> the internal repository manager
> This gives a free, self-hosted vulnerability check of the dependencies, with
> the Camel specific parts on top (Camel advisories, which components the
> routes use, the Camel version that fixes it), without a commercial SCA
> product or an API key.
> h4. Risks / tests
> * The local matching must agree with the OSV.dev API: test a set of known
> vulnerable GAVs (e.g. commons-text 1.9, snakeyaml 1.33, commons-lang3 3.12.0)
> against the answers of the API.
> * Recommend this mode for CI; keep the live API the default for quick local
> use, and the current {{--offline}} (Camel advisories only) as is.
> * Document the URL, the cache and the refresh.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)