What is CVE-2022-39294?

CVE-2022-39294 is a high-severity uncontrolled resource consumption vulnerability in conduit-hyper (rust), affecting versions >= 0.2.0-alpha.3, < 0.4.2. It is fixed in 0.4.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2022-39294?

CVE-2022-39294 has a CVSS score of 7.5 (High). 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.

Which versions of conduit-hyper are affected by CVE-2022-39294?

conduit-hyper (rust) versions >= 0.2.0-alpha.3, < 0.4.2 is affected.

Is there a fix for CVE-2022-39294?

Yes. CVE-2022-39294 is fixed in 0.4.2. Upgrade to this version or later.

Is CVE-2022-39294 exploitable, and should I be worried?

Whether CVE-2022-39294 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.

What actually determines whether CVE-2022-39294 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.

CVE-2022-39294 in conduit-hyper

Q: How severe is CVE-2022-39294?

CVE-2022-39294 has a CVSS score of 7.5 (High). 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.

Q: Which versions of conduit-hyper are affected by CVE-2022-39294?

conduit-hyper (rust) versions >= 0.2.0-alpha.3, < 0.4.2 is affected.

Q: Is there a fix for CVE-2022-39294?

Yes. CVE-2022-39294 is fixed in 0.4.2. Upgrade to this version or later.

Q: Is CVE-2022-39294 exploitable, and should I be worried?

Whether CVE-2022-39294 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.

Q: What actually determines whether CVE-2022-39294 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.

Q: How do I fix CVE-2022-39294?

Upgrade conduit-hyper to 0.4.2 or later.

Summary

conduit-hyper vulnerable to Denial of Service from unchecked request length

Prior to version 0.4.2, conduit-hyper did not check any limit on a request's length before calling hyper::body::to_bytes. An attacker could send a malicious request with an abnormally large Content-Length, which could lead to a panic if memory allocation failed for that request.

In version 0.4.2, conduit-hyper sets an internal limit of 128 MiB per request, otherwise returning status 400 ("Bad Request").

This crate is part of the implementation of Rust's crates.io, but that service is not affected due to its existing cloud infrastructure, which already drops such malicious requests. Even with the new limit in place, conduit-hyper is not recommended for production use, nor to directly serve the public Internet.

The vulnerability was discovered by Ori Hollander from the JFrog Security Research team.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2022-39294 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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.4.2); upgrading removes the vulnerable code path.

Affected versions

conduit-hyper (>= 0.2.0-alpha.3, < 0.4.2)

Security releases

conduit-hyper → 0.4.2 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade conduit-hyper to 0.4.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-39294? CVE-2022-39294 is a high-severity uncontrolled resource consumption vulnerability in conduit-hyper (rust), affecting versions >= 0.2.0-alpha.3, < 0.4.2. It is fixed in 0.4.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is CVE-2022-39294? CVE-2022-39294 has a CVSS score of 7.5 (High). 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.
Which versions of conduit-hyper are affected by CVE-2022-39294? conduit-hyper (rust) versions >= 0.2.0-alpha.3, < 0.4.2 is affected.
Is there a fix for CVE-2022-39294? Yes. CVE-2022-39294 is fixed in 0.4.2. Upgrade to this version or later.
Is CVE-2022-39294 exploitable, and should I be worried? Whether CVE-2022-39294 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
What actually determines whether CVE-2022-39294 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.
How do I fix CVE-2022-39294? Upgrade conduit-hyper to 0.4.2 or later.