CVE-2015-2313
Summary
| CVE | CVE-2015-2313 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2017-08-09 18:29:00 UTC |
| Updated | 2017-08-17 14:59:00 UTC |
| Description | 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 remote peers to cause a denial of service (CPU consumption) via a crafted small message, which triggers a "tight" for loop. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-2312. |
Risk And Classification
Problem Types: CWE-400
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Capnproto | Capnproto | 0.5.0.0 | All | All | All |
| Application | Capnproto | Capnproto | 0.5.1.0 | All | All | All |
| Application | Capnproto | Capnproto | 0.5.1.1 | All | All | All |
| Application | Capnproto | Capnproto | All | All | All | All |
| Application | Capnproto | Capnproto | 0.5.0.0 | All | All | All |
| Application | Capnproto | Capnproto | 0.5.1.0 | All | All | All |
| Application | Capnproto | Capnproto | 0.5.1.1 | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| SECURITY: Additional CPU amplification case. · capnproto/capnproto@8014974 · GitHub | CONFIRM | github.com | Third Party Advisory |
| #780568 - capnproto: CVE-2015-2313: CPU usage amplification attack #2 - Debian Bug report logs | MISC | bugs.debian.org | Mailing List, Third Party Advisory |
| oss-security - Re: CVE Request: Cap'n Proto: Several issues | MLIST | www.openwall.com | Mailing List, Third Party Advisory |
| capnproto/2015-03-05-0-c++-addl-cpu-amplification.md at master · capnproto/capnproto · GitHub | CONFIRM | github.com | Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.