CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in yaml-cpp 0.6.2. This vulnerability affects the function SingleDocParser::HandleFlowSequence
of the component YAML File Handler. The manipulation leads to denial of service.
This vulnerability was named CVE-2018-20710. The attack can be initiated remotely. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as problematic has been found in yaml-cpp 0.6.2. This affects the function SingleDocParser::HandleFlowSequence
of the component YAML File Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
The SingleDocParser::HandleFlowSequence function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers to cause a denial of service (stack consumption and application crash) via a crafted YAML file.
The bug was discovered 01/14/2019. The weakness was published 03/07/2019. This vulnerability is uniquely identified as CVE-2018-20710 since 01/14/2019. It is possible to initiate the attack remotely. 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 52 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/14/2019 🔍01/14/2019 🔍
03/07/2019 🔍
03/08/2019 🔍
07/29/2023 🔍
Sources
Status: Not definedCVE: CVE-2018-20710 (🔍)
GCVE (CVE): GCVE-0-2018-20710
GCVE (VulDB): GCVE-100-131445
Entry
Created: 03/08/2019 07:19Updated: 07/29/2023 13:17
Changes: 03/08/2019 07:19 (39), 05/14/2020 16:13 (1), 07/29/2023 13:17 (9)
Complete: 🔍
Cache ID: 216:04C:103
No comments yet. Languages: en.
Please log in to comment.