oscerd opened a new issue, #137: URL: https://github.com/apache/camel-kit/issues/137
## Description `knowledge/mcp/src/main/java/org/apache/camel/kit/knowledge/mcp/IndexDownloader.java` accepts `http`, `https` and `file` schemes for the index manifest (allowlist in `releaseManifest()`, ~line 333) and derives the asset URL from it. The default is HTTPS (`https://api.github.com/repos/apache/camel-kit/releases`) and archive integrity is protected by the manifest `sha256`, so the default configuration is safe. However, if an operator sets `knowledge.index.url=http://…`, the manifest itself — which carries the expected `sha256` — is fetched over cleartext and can be tampered with in transit, defeating the integrity check (the attacker simply rewrites both the asset URL and its `sha256`). ## Proposed change For **remote** manifests/assets allow only `https`; keep `file` for the documented local/air-gapped path. Reject remote `http://` manifest/asset URLs with a clear error message. ## Notes Defense-in-depth; the default configuration is already safe. _AI-generated by Claude Code (Claude Opus 4.8) on behalf of @oscerd._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
