# CVE-2022-41939: Credential exposure when running third-party builders in knative/func

> Developers using third-party buildpacks may expose registry credentials or Docker sockets to malicious lifecycle containers.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Nov 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-5336-2g3f-9g3m

## What is CVE-2022-41939?

CVE-2022-41939 is a medium-severity vulnerability in knative func, published on 19 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-41939?

It affects 1 product.


Products: Linuxfoundation Knative Func.

## How do I fix CVE-2022-41939?

No fix has been published for CVE-2022-41939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41939 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41939 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41939 and fix it if it is affected.

What it is: CVE-2022-41939 is a medium-severity vulnerability in knative func, published on 19 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41939 exists.

Affected product: knative func. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41939/ (Markdown: https://insights.sbomify.com/CVE-2022-41939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41939
- OSV: https://osv.dev/vulnerability/CVE-2022-41939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41939/
Summaries are generated and may contain mistakes; the official description above is the record.