Repository disclosure and modification via absolute gitRepo paths
Published Mar 13, 2025 · Updated Mar 17, 2025
Improper input validation in Kubernetes Kubelet 1.32.2 and earlier allows remote authenticated users to access other pods' Git repositories. The in-tree gitRepo volume accepts an absolute local path as its repository value and passes it to git clone, exposing a same-node repository through the attacker's pod. Pod-creation permission and co-location on the victim node are required; repository contents can be read or modified, while service availability is unaffected.
Summary
What happened
Improper input validation in Kubernetes Kubelet 1.32.2 and earlier allows remote authenticated users to access other pods' Git repositories. The in-tree gitRepo volume accepts an absolute local path as its repository value and passes it to git clone, exposing a same-node repository through the attacker's pod. Pod-creation permission and co-location on the victim node are required; repository contents can be read or modified, while service availability is unaffected.
The record
- CVE
- CVE-2025-1767
- Published
- Mar 13, 2025
- Updated
- Mar 17, 2025
- Vendor
- Kubernetes
- Product
- Kubelet
- Classifications
- CWE-20, T1565.001, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 13, 2025CVE publishedPublication date reported by the CVE source.
- Mar 17, 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=<=v1.32.2
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