Authenticated resource exhaustion via unvalidated Git credentials
Published Feb 7, 2023 · Updated Mar 25, 2025
Injection in Rancher Wrangler allows remote authenticated users to exhaust CPU and memory via crafted Git credentials. The Git command wrapper interpolates the password into an unquoted shell command and passes repository fields without option terminators. Low-privileged access that submits credentials for either public or private repository operations is sufficient to exhaust application resources.
Summary
What happened
Injection in Rancher Wrangler allows remote authenticated users to exhaust CPU and memory via crafted Git credentials. The Git command wrapper interpolates the password into an unquoted shell command and passes repository fields without option terminators. Low-privileged access that submits credentials for either public or private repository operations is sufficient to exhaust application resources.
The record
- CVE
- CVE-2022-43756
- Published
- Feb 7, 2023
- Updated
- Mar 25, 2025
- Vendor
- NeuVector
- Product
- Rancher
- Classifications
- CWE-74, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 7, 2023CVE publishedPublication date reported by the CVE source.
- Mar 25, 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=wrangler <=0.7.3
What conditions does exploitation require?
What is affected?
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