{"answers":{"affected":"1 open source package ship an affected version, including quinn-proto.","exploited":"There is no known exploitation of RUSTSEC-2026-0342 in the wild and no public exploit code.","fix":"Upgrade quinn-proto to 0.11.17 or later.","what":"RUSTSEC-2026-0342 is a denial of service vulnerability in quinn-proto, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0342 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0342 is a denial of service vulnerability in quinn-proto, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0342 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- quinn-proto (crates.io): affected from 0.5.0; fixed in 0.11.17\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0342/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0342/index.md)","id":"RUSTSEC-2026-0342","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0342/index.md","name":"RUSTSEC-2026-0342","record":{"aliases":["GHSA-2hv7-gw8g-gpq5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust QUIC library","requires_auth":"none","summary":"Remote attackers can cause denial of service by sending empty DATAGRAM frames that bypass buffer limits, exhausting memory in applications using quinn-proto.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"quinn-proto bounds its queue of received datagrams by charging each queued frame's payload length\nagainst `TransportConfig::datagram_receive_buffer_size`, evicting the oldest datagrams when the\nlimit is exceeded. A DATAGRAM frame with an empty payload was charged zero bytes, so it never\ntriggered eviction and was appended to the queue, which has no other bound.\n\nDATAGRAM frames are not subject to flow control. A peer that has completed the handshake can\ntherefore send a stream of empty DATAGRAM frames and grow the receiver's heap without limit until\nthe process is killed. An application that reads incoming datagrams but does so more slowly than\nthe peer sends them is still affected. Receiving datagrams is enabled by default, so all endpoints\nthat do not explicitly set `datagram_receive_buffer_size(None)` are affected.\n\nThe send path had the same accounting flaw: an application could enqueue an unbounded number of\nempty outgoing datagrams without ever receiving `SendDatagramError::Blocked`.\n\nThe flaw was corrected in 0.11.17 by accounting for the fixed per-datagram overhead in both\ndirections, so that every queued datagram consumes buffer space.\n\nThanks to [@alexpyattaev](https://github.com/alexpyattaev) for reporting this issue.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Zero-length DATAGRAM frames bypass the receive buffer limit in quinn-proto","id":"RUSTSEC-2026-0342","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.11.17"],"introduced":["0.5.0"],"last_affected":[],"package":"quinn-proto","purl":"pkg:cargo/quinn-proto","source":"RUSTSEC-2026-0342"}],"products":null,"published":"2026-08-17","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Remote attackers can cause denial of service by sending empty DATAGRAM frames that bypass buffer limits, exhausting memory in applications using quinn-proto.","url":"https://insights.sbomify.com/RUSTSEC-2026-0342/"}