CVE-2022-43756

Denial of service (DoS) when processing Git credentials

Workarounds

A workaround is to sanitize input passed to the Git package to remove potential unsafe and ambiguous characters. Otherwise, the best course of action is to update to a patched Wrangler version.

For more information

If you have any questions or comments about this advisory:

• Reach out to SUSE Rancher Security team for security related inquiries.
• Open an issue in Rancher or Wrangler repository.
• Verify our support matrix and product support lifecycle.

A denial of services (DoS) vulnerability was discovered in Wrangler Git package affecting versions up to and including v1.0.0.

Specially crafted Git credentials can result in a denial of service (DoS) attack on an application that uses Wrangler due to the exhaustion of the available memory and CPU resources. This is caused by a lack of input validation of Git credentials before they are used, which may lead to a denial of service in some cases. This issue can be triggered when accessing both private and public Git repositories.

CVE-2022-43756 has a CVSS score of 5.9 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.7.4-security1, 0.8.5-security1, 1.0.1, 0.8.11); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched versions include v1.0.1 and later and the backported tags - v0.7.4-security1, v0.8.5-security1 and v0.8.11.

1. What is CVE-2022-43756? CVE-2022-43756 is a medium-severity security vulnerability in github.com/rancher/wrangler (go), affecting versions <= 0.7.3. It is fixed in 0.7.4-security1, 0.8.5-security1, 1.0.1, 0.8.11.
2. How severe is CVE-2022-43756? CVE-2022-43756 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/rancher/wrangler are affected by CVE-2022-43756? github.com/rancher/wrangler (go) versions <= 0.7.3 is affected.
4. Is there a fix for CVE-2022-43756? Yes. CVE-2022-43756 is fixed in 0.7.4-security1, 0.8.5-security1, 1.0.1, 0.8.11. Upgrade to this version or later.
5. Is CVE-2022-43756 exploitable, and should I be worried? Whether CVE-2022-43756 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-43756 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-43756?
   • Upgrade github.com/rancher/wrangler to 0.7.4-security1 or later
   • Upgrade github.com/rancher/wrangler to 0.8.5-security1 or later
   • Upgrade github.com/rancher/wrangler to 1.0.1 or later
   • Upgrade github.com/rancher/wrangler to 0.8.11 or later

Other vulnerabilities in github.com/rancher/wrangler