GHSA-fmwf-c46w-r8qm: Qcp Denial of Service Vulnerability

MODERATE
Published
Advisory Summary

GHSA-fmwf-c46w-r8qm is a MODERATE denial of service vulnerability (General Security Weakness) affecting Qcp libraries in the crates.io ecosystem. The issue involves qcp has possible crash/dos in some build configurations. Remediation is available by upgrading affected packages to version 0.3.3.

GHSA-fmwf-c46w-r8qm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-fmwf-c46w-r8qm
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Qcp
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-fmwf-c46w-r8qm

To remediate this vulnerability, upgrade all affected Qcp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

qcp fixed: 0.3.3
Upgrade qcp to 0.3.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for qcp

How to Check if You Are Affected

To determine whether your application is affected by GHSA-fmwf-c46w-r8qm, inspect your project dependencies for Qcp:

inspect dependencies for qcp

Analyze the terminal output to locate any version of Qcp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.3.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Qcp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**Nature of issue:** Crash (Denial of Service) **Source of issue:** Dependent package (ring) **Affected versions of qcp:** 0.1.0-0.3.2 **Recommendation:** Upgrade to qcp 0.3.3 or later ### Who is affected All versions of qcp from 0.1.0 to 0.3.2 are affected, but **only if built with runtime overflow checks.** * Released qcp binaries do not enable runtime overflow checks by default. **If you use an official released qcp binary download, you are not affected.** * If you built qcp yourself in debug mode, you are affected unless your debug configuration explicitly disables overflow checks. * If you built qcp yourself in release mode, you are only affected if you explicitly requested runtime overflow checks at build time by setting the appropriate `RUSTFLAGS`, or in your Cargo.toml profile. ### What to do if you are affected **We recommend you upgrade to qcp 0.3.3 or later.** Users upgrading from versions prior to 0.3.0 should note that an incompatible protocol change was introduced in version 0.3.0, so should stage their upgrade carefully. Alternatively, it is possible to avoid upgrading by rebuilding qcp locally. The following alternative mitigations have been identified: * Rebuild locally with runtime overflow checks disabled * Rebuild locally using a fixed version of the `ring` dependency (0.17.12 or later). ### Detail The upstream advisory describes a crash in the implementation of the QUIC protocol that can be induced by a specially-crafted packet, and which happens naturally approximately every 1 in 2**32 packets sent and/or received. The crash only happens when runtime overflow checking is enabled. Note that the upstream advisory describes the overflow check causing this issue as "unwanted". Their response, to remove the overflow check in one place, does not introduce any additional issue. ### Impact During qcp file transfer sessions, it is possible for an attacker to send a specially-crafted packet that could trigger this issue. * In that case, and only if qcp was built with runtime overflow checks enabled, the effect is a Rust panic which immediately aborts the transfer. There is no additional impact on system resources at either end, nor on other file transfers in progress. * As qcp runs a separate process for every connected user, the impact of the attack is limited to a single session. The underlying issue may also affect particularly large file transfers. The maximum TLS packet size is 16KB, so 2**32 packets will transfer up to 68TB (including the protocol/retransmit overhead). Again, this is only the case if qcp was built with runtime overflow checks enabled. As of the time of writing, we are not aware of any reports of this issue being exploited. #### Additional notes * The qcp protocol itself does not rely on runtime overflow checks for its security. * While QUIC servers are normally public-facing, [qcp is a hybrid protocol](https://docs.rs/qcp/latest/qcp/protocol/index.html) that first requires an authenticated ssh session in order to set up the QUIC session. The window of attackability is therefore reduced, though will depend on your usage profile. * An additional layer of obscurity is provided by qcp using ephemeral, random port numbers for its QUIC traffic (subject to user configuration). ### References Upstream advisories: * [RUSTSEC-2025-0009](https://rustsec.org/advisories/RUSTSEC-2025-0009.html) * https://github.com/advisories/GHSA-4p46-pwfr-66x6

GHSA-fmwf-c46w-r8qm Affected Qcp Versions

1 component(s)
Fixed Versions:
0.3.3
Product / Package Ecosystem Affected Versions Fixed Version
qcp
crates.io
< 0.3.3
0.3.3

References

Frequently Asked Questions

What is GHSA-fmwf-c46w-r8qm?
GHSA-fmwf-c46w-r8qm is a security vulnerability in Qcp involving qcp has possible crash/DOS in some build configurations under General Security Weakness.
Which Qcp versions are affected?
Affected versions include releases prior to 0.3.3 across affected packages: qcp.
What version fixes GHSA-fmwf-c46w-r8qm?
Upgrading to 0.3.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is qcp affected?
Yes, qcp is affected in releases prior to 0.3.3. Upgrade your dependency to 0.3.3 or later.
What CWE is associated with GHSA-fmwf-c46w-r8qm?
GHSA-fmwf-c46w-r8qm is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-fmwf-c46w-r8qm?
Run the dependency tree command: 'inspect dependencies for qcp'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fmwf-c46w-r8qm",
  "modified" : "2025-03-08T01:30:18Z",
  "published" : "2025-03-08T01:30:18Z",
  "aliases" : [ ],
  "summary" : "qcp has possible crash/DOS in some build configurations",
  "details" : "**Nature of issue:** Crash (Denial of Service)\n**Source of issue:** Dependent package (ring)\n**Affected versions of qcp:** 0.1.0-0.3.2\n**Recommendation:** Upgrade to qcp 0.3.3 or later\n\n### Who is affected\n\nAll versions of qcp from 0.1.0 to 0.3.2 are affected, but **only if built with runtime overflow checks.**\n\n* Released qcp binaries do not enable runtime overflow checks by default. **If you use an official released qcp binary download, you are not affected.**\n* If you built qcp yourself in debug mode, you are affected unless your debug configuration explicitly disables overflow checks.\n* If you built qcp yourself in release mode, you are only affected if you explicitly requested runtime overflow checks at build time by setting the appropriate `RUSTFLAGS`, or in your Cargo.toml profile.\n\n### What to do if you are affected\n\n**We recommend you upgrade to qcp 0.3.3 or later.**\nUsers upgrading from versions prior to 0.3.0 should note that an incompatible protocol change was introduced in version 0.3.0, so should stage their upgrade carefully.\n\nAlternatively, it is possible to avoid upgrading by rebuilding qcp locally. The following alternative mitigations have been identified:\n* Rebuild locally with runtime overflow checks disabled\n* Rebuild locally using a fixed version of the `ring` dependency (0.17.12 or later).\n\n### Detail\n\nThe upstream advisory describes a crash in the implementation of the QUIC protocol that can be induced by a specially-crafted packet, and which happens naturally approximately every 1 in 2**32 packets sent and/or received.\n\nThe crash only happens when runtime overflow checking is enabled. Note that the upstream advisory describes the overflow check causing this issue as \"unwanted\". Their response, to remove the overflow check in one place, does not introduce any additional issue.\n\n### Impact\n\nDuring qcp file transfer sessions, it is possible for an attacker to send a specially-crafted packet that could trigger this issue.\n* In that case, and only if qcp was built with runtime overflow checks enabled, the effect is a Rust panic which immediately aborts the transfer. There is no additional impact on system resources at either end, nor on other file transfers in progress.\n* As qcp runs a separate process for every connected user, the impact of the attack is limited to a single session.\n\nThe underlying issue may also affect particularly large file transfers. The maximum TLS packet size is 16KB, so 2**32 packets will transfer up to 68TB (including the protocol/retransmit overhead). Again, this is only the case if qcp was built with runtime overflow checks enabled.\n\nAs of the time of writing, we are not aware of any reports of this issue being exploited.\n\n#### Additional notes\n* The qcp protocol itself does not rely on runtime overflow checks for its security.\n* While QUIC servers are normally public-facing, [qcp is a hybrid protocol](https://docs.rs/qcp/latest/qcp/protocol/index.html) that first requires an authenticated ssh session in order to set up the QUIC session. The window of attackability is therefore reduced, though will depend on your usage profile.\n* An additional layer of obscurity is provided by qcp using ephemeral, random port numbers for its QUIC traffic (subject to user configuration).\n\n### References\nUpstream advisories:\n* [RUSTSEC-2025-0009](https://rustsec.org/advisories/RUSTSEC-2025-0009.html)\n* https://github.com/advisories/GHSA-4p46-pwfr-66x6",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "qcp"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.3.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/crazyscot/qcp/security/advisories/GHSA-fmwf-c46w-r8qm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-4p46-pwfr-66x6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/briansmith/ring/blob/main/RELEASES.md#version-01712-2025-03-05"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/crazyscot/qcp"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2025-0009.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-08T01:30:18Z",
    "nvd_published_at" : null
  }
}