CVE-2019-6292 (Medium) detected in yaml-cppyaml-cpp-0.6.3

[mend-bolt-for-github[bot]]

CVE-2019-6292 - Medium Severity Vulnerability

Vulnerable Library - yaml-cppyaml-cpp-0.6.3

A YAML parser and emitter in C++

Library home page: https://github.com/jbeder/yaml-cpp.git

Found in HEAD commit: 8677308245a2cb3d6d333bdf06e564b7b4592f4c

Found in base branch: main

Vulnerable Source Files (2)

/src/third_party/yaml-cpp-0.6.2/yaml-cpp/src/singledocparser.cpp /src/third_party/yaml-cpp-0.6.2/yaml-cpp/src/singledocparser.cpp

Vulnerability Details

An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2. Stack Exhaustion occurs in YAML::SingleDocParser, and there is a stack consumption problem caused by recursive stack frames: HandleCompactMap, HandleMap, HandleFlowSequence, HandleSequence, HandleNode. Remote attackers could leverage this vulnerability to cause a denial-of-service via a cpp file.

Publish Date: 2022-10-03

URL: CVE-2019-6292

CVSS 3 Score Details (6.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://nvd.nist.gov/vuln/detail/CVE-2019-6292

Release Date: 2020-08-24

Fix Resolution: libyaml-cpp0.3 - 0.6.3-1,0.6.3-1;libyaml-cpp0.5 - 0.6.3-1,0.6.3-1;libyaml-cpp0.6 - 0.6.3-1,0.6.3-1;libyaml-cpp-dev - 0.6.3-1,0.6.3-1;libyaml-cpp0.5v5 - 0.6.3-1,0.6.3-1

---

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github[bot]]

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-bolt-for-github[bot]]

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-bolt-for-github[bot]]

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-bolt-for-github[bot]]

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-bolt-for-github[bot]]

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.