yaml-cpp project vulnerabilities
Recent CVEs affecting yaml-cpp project products. 4 tracked.
yaml-cpp project has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-01-15. Highest priority: CVE-2019-6285 (score 49/100).
- CVE-2019-6292 MEDIUM 6.5 DOWNGRADE An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2
- CVE-2019-6285 MEDIUM 6.5 DOWNGRADE The SingleDocParser::HandleFlowSequence function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers t
- CVE-2018-20574 MEDIUM 6.5 DOWNGRADE The SingleDocParser::HandleFlowMap function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers to cau
- CVE-2018-20573 MEDIUM 6.5 DOWNGRADE The Scanner::EnsureTokensInQueue function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers to cause
FAQ
How do I fix yaml-cpp project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is yaml-cpp project being exploited right now?
None of the tracked yaml-cpp project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which yaml-cpp project CVE should I patch first?
CVE-2019-6285 currently ranks highest (49/100): The SingleDocParser::HandleFlowSequence function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers t.