Credential exposure via spoofed builder image prefix
Published Nov 19, 2022 · Updated Apr 22, 2025
Sensitive information exposure in Knative Functions before 1.8.1 allows attackers to read registry credentials during function builds. The builder allowlist accepts image-name prefixes without a trailing slash, so a spoofed repository passes the trusted-prefix check and supplies an attacker-controlled lifecycle container. A developer must select a third-party builder and trigger func build, run, or remote push; the lifecycle then receives mounted registry credentials or the local Docker socket.
Summary
What happened
Sensitive information exposure in Knative Functions before 1.8.1 allows attackers to read registry credentials during function builds. The builder allowlist accepts image-name prefixes without a trailing slash, so a spoofed repository passes the trusted-prefix check and supplies an attacker-controlled lifecycle container. A developer must select a third-party builder and trigger func build, run, or remote push; the lifecycle then receives mounted registry credentials or the local Docker socket.
The record
- CVE
- CVE-2022-41939
- Published
- Nov 19, 2022
- Updated
- Apr 22, 2025
- Vendor
- Knative
- Product
- Knative Functions
- Classifications
- CWE-200, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.8.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo