CVE-2022-41939: Credential exposure when running third-party builders in knative/func
knative.dev/func is is a client library and CLI enabling the development and deployment of Kubernetes functions. Developers using a malicious or compromised third-party buildpack could expose their registry credentials or local docker socket to a malicious lifecycle container. This issues has been patched in PR #1442, and is part of release 1.8.1. This issue only affects users who are using function buildpacks from third-parties; pinning the builder image to a specific content-hash with a valid lifecycle image will also mitigate the attack.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
knative.dev/functo a version that resolves this vulnerability.Fixed in 1.8.1Patch PR #1442 - Compensating control
Pin the builder image to a specific content-hash and ensure a valid `lifecycle` image is used to mitigate the risk when using third-party function buildpacks.
Event History
Frequently Asked Questions
What is the severity of CVE-2022-41939?
CVE-2022-41939 is classified as a high severity vulnerability due to the potential exposure of sensitive credentials.
How do I fix CVE-2022-41939?
To mitigate CVE-2022-41939, upgrade to Knative Func version 1.8.1 or later.
What type of software is affected by CVE-2022-41939?
CVE-2022-41939 affects the Knative Func client library and CLI, specifically versions prior to 1.8.1.
What vulnerabilities does CVE-2022-41939 introduce?
CVE-2022-41939 introduces the risk of exposing registry credentials or a local Docker socket to malicious containers.
Who is impacted by CVE-2022-41939?
Developers using a malicious or compromised third-party buildpack with Knative Func are significantly impacted by CVE-2022-41939.