CVE-2015-2311 json
Integer 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…
published 9y ago modified 4mo ago also EUVD-2015-2406
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Integer 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 possibly obtain sensitive information from memory or execute arbitrary code via a crafted message.
Patch / fix
- capnproto Debian 14, Debian 13, Debian 12 0.4.1-3
debian advisories DEBIAN-CVE-2015-2311
- capnproto Ubuntu 14.04 LTS 0.4.0-1ubuntu2.1
ubuntu advisories UBUNTU-CVE-2015-2311
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2015-2311 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.54% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-191 Integer Underflow (Wrap or Wraparound)
References
-
github.com
/capnproto/capnproto/commit/26bcceda72372211063d62aab7e45665faa83633
third-party-advisory
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=780566
mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2015/03/17/3
mailing-list, third-party-advisory
-
github.com
/capnproto/capnproto/blob/master/security-advisories/2015-03-02-1-c%2B%2B-integer-underflow.md
third-party-advisory
Sources
- CVE List CVE-2015-2311
- NVD CVE-2015-2311
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.