Sandstorm Cap'n Proto up to 0.4.1.0/0.5.1.0 Incomplete Fix totalSize Application resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Sandstorm Cap'n Proto up to 0.4.1.0/0.5.1.0. This vulnerability affects the function totalSize of the component Incomplete Fix. Performing a manipulation as part of Application results in resource consumption.
This vulnerability is identified as CVE-2015-2313. The attack can be initiated remotely. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Sandstorm Cap'n Proto up to 0.4.1.0/0.5.1.0. This affects the function totalSize of the component Incomplete Fix. The manipulation as part of a Application leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
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.
The bug was discovered 03/17/2015. The weakness was released 08/09/2017 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2015-2313 since 03/17/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 876 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.4.1.1 or 0.5.1.1 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-105138, VDB-105139 and VDB-105140. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Cap'n Proto 0.4.1.1/0.5.1.1
Patch: github.com
Timeline
03/17/2015 🔍03/17/2015 🔍
08/09/2017 🔍
08/09/2017 🔍
08/10/2017 🔍
12/15/2022 🔍
Sources
Advisory: 80149744bdafa3ad4eedc83f8ab675e27baee868Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-2313 (🔍)
GCVE (CVE): GCVE-0-2015-2313
GCVE (VulDB): GCVE-100-105141
See also: 🔍
Entry
Created: 08/10/2017 08:30Updated: 12/15/2022 14:47
Changes: 08/10/2017 08:30 (62), 11/05/2019 17:27 (1), 12/15/2022 14:47 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.