PatchTheCVEyaml-cpp vulnerabilities and fixes
Recent CVEs affecting yaml-cpp, with upgrade or downgrade steps. 6 tracked.
Also searched as: yaml cpp.
yaml-cpp has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-01-15. Highest priority: CVE-2017-11692 (score 57/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
- CVE-2017-5950 MEDIUM 5.5 DOWNGRADE The SingleDocParser::HandleNode function in yaml-cpp (aka LibYaml-C++) 0.5.3 allows remote attackers to cause
- CVE-2017-11692 HIGH 7.5 UPGRADE The function "Token& Scanner::peek" in scanner.cpp in yaml-cpp 0.5.3 and earlier allows remote attackers to ca
FAQ
How do I fix yaml-cpp 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 being exploited right now?
None of the tracked yaml-cpp CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which yaml-cpp CVE should I patch first?
CVE-2017-11692 currently ranks highest (57/100): The function "Token& Scanner::peek" in scanner.cpp in yaml-cpp 0.5.3 and earlier allows remote attackers to ca.