GHSA-4W2J-M93H-CJ5J

Quinn: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly

The Assembler component that assembles unordered stream fragments into consecutive chunks of the stream incurs some overhead for non-contiguous fragments. Readers that read from a RecvStream in order (through an AsyncRead impl for example) will be sensitive to peers that send fragments while leaving out early parts of the stream, and in particular, fragments with many gaps (because these cannot be defragmented). In such a scenario, the receiving connection suffers from high buffer overhead, enabling memory exhaustion.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

GHSA-4W2J-M93H-CJ5J 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.11.15); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-4W2J-M93H-CJ5J? GHSA-4W2J-M93H-CJ5J is a high-severity allocation of resources without limits or throttling vulnerability in quinn-proto (rust), affecting versions >= 0.1.0, < 0.11.15. It is fixed in 0.11.15. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is GHSA-4W2J-M93H-CJ5J? GHSA-4W2J-M93H-CJ5J 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.
3. Which versions of quinn-proto are affected by GHSA-4W2J-M93H-CJ5J? quinn-proto (rust) versions >= 0.1.0, < 0.11.15 is affected.
4. Is there a fix for GHSA-4W2J-M93H-CJ5J? Yes. GHSA-4W2J-M93H-CJ5J is fixed in 0.11.15. Upgrade to this version or later.
5. Is GHSA-4W2J-M93H-CJ5J exploitable, and should I be worried? Whether GHSA-4W2J-M93H-CJ5J 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 GHSA-4W2J-M93H-CJ5J 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 GHSA-4W2J-M93H-CJ5J? Upgrade quinn-proto to 0.11.15 or later.

Other vulnerabilities in quinn-proto