Yaml-Cpp

Every one of the 6 is a mark on the map. Named now: 1 to 6, most at risk first.

1. 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)…CVE-2019-6285Yaml-Cpp Project · 2.5% likely

   CWE-674

2. The SingleDocParser::HandleFlowMap 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…CVE-2018-20574Yaml-Cpp Project · 2.5% likely

   CWE-119

3. The Scanner::EnsureTokensInQueue 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…CVE-2018-20573Yaml-Cpp Project · 2.5% likely

   CWE-119

4. The function "Token& Scanner::peek" in scanner.cpp in yaml-cpp 0.5.3 and earlier allows remote attackers to cause a denial of service (assertion failure and application exit) via…CVE-2017-11692Yaml-Cpp Project · 2.2% likely

   CWE-617

5. The SingleDocParser::HandleNode function in yaml-cpp (aka LibYaml-C++) 0.5.3 allows remote attackers to cause a denial of service (stack consumption and application crash) via a c…CVE-2017-5950Yaml-Cpp Project · 2.0% likely

   CWE-119

6. 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 caus…CVE-2019-6292Yaml-Cpp Project · 1.9% likely

   CWE-674

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.