AI analysis
Apache Camel K, the Kubernetes-native integration runtime for Apache Camel, has an authorization flaw (CWE-639, user-controlled key) in its custom resource resolution: tenant-supplied values, such as the Builder trait's mavenProfiles ValueSources, cause the operator to resolve secrets by name from the operator's namespace instead of the tenant's own namespace. A tenant that can set a secret name on an Integration build resource can therefore have the operator pull in a secret belonging to another tenant or to operator components. An attacker with tenant-level access gains access to those secrets, potentially obtaining credentials shared across the multi-tenant cluster. Users running Apache Camel K 2.0.0 through 2.9.2 or version 2.10.1 are affected; fixes are available in 2.9.3, 2.10.2, and 2.11.0. No public proof of concept exists, the issue is not in CISA KEV, and no in-the-wild exploitation is known.
What to do: Upgrade to Apache Camel K 2.9.3, 2.10.2, or 2.11.0. As interim mitigation, review tenant-authored Integrations for secret references that resolve in the operator namespace (particularly Builder trait mavenProfiles ValueSources), restrict tenants from naming operator-namespace secrets, and rotate any sensitive secrets in the operator namespace that tenants could have referenced.
Affected
| Apache Camel K | >= 2.0.0 and < 2.9.3 (fixed in 2.9.3) |
| Apache Camel K | 2.10.1 (fixed in 2.10.2); 2.11.0 is unaffected |
Estimated exposure
nicheunknown; plausibly on the order of hundreds to a few thousand Kubernetes clusters, likely far fewer in strictly multi-tenant configurations where the flaw… — Camel K is a specialized, enterprise-oriented Apache integration-runtime operator (not the widely used Camel libraries) with no public install-count or internet-exposure scan data, so the affected base is small and multi-tenant deployments…
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
Authorization bypass through User-Controlled key vulnerability in Apache Camel K. An authorization vulnerability in custom resource resolution allows a tenant to reference secrets by name in the operator namespace, potentially exposing secrets belonging to other tenants or operator components. This issue affects Apache Camel K: from 2.0.0 before 2.9.3, from 2.10.1 before 2.10.2. Users are recommended to upgrade to version 2.9.3, 2.10.2 or 2.11.0, which fixes the issue.