Threat Intelligence Database

Apache Camel Karavan versions from 4.0.0 up to but not including 4.22.1 contain an improper input validation vulnerability. This flaw allows an authenticated user of any role to deploy arbitrary Kubernetes resources by submitting a crafted kubernetes.yaml file. The vulnerability arises because Karavan applies all resources in the deployment file without restricting resource kinds, rejecting security-sensitive pod options, or pinning the namespace. This can lead to the creation of privileged pods and other risky configurations within the cluster. The issue is fixed in version 4.22.1.

Apache Camel Karavan versions from 3.18.0 up to but not including 4.22.1 contain a path traversal vulnerability. This flaw allows an authenticated user to supply a project file name containing '../' sequences, causing files to be written outside the intended project directory. Exploitation can lead to overwriting application configuration or classpath files, enabling code execution within the Karavan container. The issue is fixed in version 4.22.1.

Improper input validation vulnerability in Apache Camel Karavan. When a deployment was started, Karavan unmarshalled a project's `kubernetes.yaml` and applied every resource it contained to the cluster without restricting the resource kinds, without rejecting security-sensitive pod options, and without pinning the target namespace. An authenticated user of any role could therefore have Karavan apply arbitrary Kubernetes resources within the reach of its service account, including pods requesting hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation or added capabilities. This issue affects Apache Camel Karavan: from 4.0.0 before 4.22.1. Users are recommended to upgrade to version 4.22.1, which fixes the issue.

Improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Apache Camel Karavan. A project file name supplied through the project file API was used verbatim as a path segment when the project was written to the working copy for a Git commit, so a name containing `../` sequences caused the file content to be written outside the project directory, to any location writable by the Karavan process. An authenticated user of any role could use this to overwrite application configuration or files on the application classpath and so execute code in the Karavan container. This issue affects Apache Camel Karavan: from 3.18.0 before 4.22.1. Users are recommended to upgrade to version 4.22.1, which fixes the issue.