Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.93% (FIRST EPSS); higher than 60.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: capnp (crates.io) 0.13.7, 0.14.11, 0.15.2; capnproto (Debian:12) 0.9.2-2; rust-capnp (Debian:12) 0.14.11-1.1.

Low priority for now. Upgrade to capnp (crates.io) 0.13.7, 0.14.11, 0.15.2; capnproto (Debian:12) 0.9.2-2; rust-capnp (Debian:12) 0.14.11-1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.4 · v3.1—No exploit Fix available
Published
Nov 30, 2022
Updated
Jun 17, 2026
EPSS
0.9% · 60th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.4
CNA · GitHub_M
5.4
agree

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-46149

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
capnprotocapnproto
capnprotocapnp
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • capnproto capnp0.15.0 and later · before 0.15.2
  • capnproto capnpbefore 0.13.7
  • capnproto capnp0.14.0 and later · before 0.14.11
  • capnproto capnprotobefore 0.7.1
  • capnproto capnproto0.9.0 and later · before 0.9.2
  • capnproto capnproto0.10.0 and later · before 0.10.3
  • capnproto capnproto0.8.0
  • fedoraproject fedora36
  • fedoraproject fedora37

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • capnproto capnproto

    • < 0.7.1, >= 0.8.0, < 0.8.1, >= 0.9.0, < 0.9.2, >= 0.10.0, < 0.10.3, >= 0.13.0, < 0.13.7, >= 0.14.0, < 0.14.11, >= 0.15.0, < 0.15.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.iocapnpfrom 0.0.0-0 · before 0.13.70.13.7
crates.iocapnpfrom 0.14.0 · before 0.14.110.14.11
crates.iocapnpfrom 0.14.0-0 · before 0.14.110.14.11
crates.iocapnpfrom 0.15.0 · before 0.15.20.15.2
crates.iocapnpfrom 0.15.0-0 · before 0.15.20.15.2
crates.iocapnpbefore 0.13.70.13.7
Debian:12capnprotobefore 0.9.2-20.9.2-2
Debian:12rust-capnpbefore 0.14.11-1.10.14.11-1.1
openSUSE:Leap 15.4capnprotobefore 0.9.1-150400.3.4.10.9.1-150400.3.4.1
openSUSE:Tumbleweedpython-pycapnpbefore 2.0.0-2.52.0.0-2.5
Red Hat:openshift:4.12::el8conmon-rsbefore 0:0.5.1-3.rhaos4.12.git.el80:0.5.1-3.rhaos4.12.git.el8
Red Hat:openshift:4.12::el9conmon-rsbefore 0:0.5.1-3.rhaos4.12.git.el90:0.5.1-3.rhaos4.12.git.el9
SUSE:Linux Enterprise Module for Desktop Applications 15 SP4capnprotobefore 0.9.1-150400.3.4.10.9.1-150400.3.4.1

Other highest-scoring records for the same primary product.

  • CVE-2023-48230Cap'n Proto WebSocket message can cause crash
    40Plan
  • CVE-2015-2311Integer underflow in Sandstorm Cap'n Proto before 0.4.1.1 and 0.5.x before 0.5.1.1 might allow remote peers to cause a denial of service or
    40Plan
  • CVE-2015-2310Integer overflow in layout.c++ in Sandstorm Cap'n Proto before 0.4.1.1 and 0.5.x before 0.5.1.1 allows remote peers to cause a denial of ser
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2015-2312Aug 9, 2017 · Sandstorm Cap'n Proto before 0.4.1.1 and 0.5.x before 0.5.1.1 allows remote peers to cause a denial of service (CPU and possibly general res
    31Monitor
  • ← EarlierCVE-2015-2313Aug 9, 2017 · Sandstorm Cap'n Proto before 0.4.1.1 and 0.5.x before 0.5.1.2, when an application invokes the totalSize method on an object reader, allows
    31Monitor
  • Later →CVE-2026-32239Mar 12, 2026 · Cap'n Proto has an integer overflow in KJ-HTTP
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
crates.io:capnp0.13.7Package registry (OSV)
crates.io:capnp0.14.11Package registry (OSV)
crates.io:capnp0.15.2Package registry (OSV)
debian:capnproto0.9.2-2 · Debian:12Package registry (OSV)
debian:rust-capnp0.14.11-1.1 · Debian:12Package registry (OSV)
opensuse:capnproto0.9.1-150400.3.4.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:python-pycapnp2.0.0-2.5 · openSUSE:TumbleweedPackage registry (OSV)
red hat:conmon-rs0:0.5.1-3.rhaos4.12.git.el8 · Red Hat:openshift:4.12::el8Package registry (OSV)
suse:capnproto0.9.1-150400.3.4.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
Low

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records