Memory Corruption

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

1. 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

2. 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

3. 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

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.