CVE-2022-46149

Cap'n Proto vulnerable to out-of-bounds read due to logic error handling list-of-list.

MEDIUM
5.4
CVSS Score
Published: November 30, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 05:11 AM UTC
3 products affected across 2 vendorsFedoraCapnprotoCapnp

Using capnproto by capnproto?

Get instant alerts when new vulnerabilities affect capnproto - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.4
Exploit prediction
EPSS 0.9%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.13.70.14.0 ≤ v < 0.14.110.15.0 ≤ v < 0.15.2
Affected range stops below 0.13.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.14.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.15.2, so it looks safe — our inference, not a vendor statement
v < 0.10.3v < 0.13.7v < 0.14.11v < 0.15.2v < 0.7.1v < 0.8.1v < 0.9.20.10.0 ≤ v < 0.10.30.9.0 ≤ v < 0.9.20.8.0
Affected range stops below 0.10.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.13.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.14.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.15.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.7.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.8.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.9.2, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.4MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card