Vulnerability Description
YamlDotNet version 4.3.2 and earlier contains a Insecure Direct Object Reference vulnerability in The default behavior of Deserializer.Deserialize() will deserialize user-controlled types in the line "currentType = Type.GetType(nodeEvent.Tag.Substring(1), throwOnError: false);" and blindly instantiates them. that can result in Code execution in the context of the running process. This attack appear to be exploitable via Victim must parse a specially-crafted YAML file. This vulnerability appears to have been fixed in 5.0.0.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Yamldotnet Project | Yamldotnet | <= 4.3.2 |
Related Weaknesses (CWE)
References
- https://github.com/aaubry/YamlDotNet#version-500Third Party Advisory
- https://github.com/aaubry/YamlDotNet/blob/f96b7cc40a0498f8bafdeb49df3aa23aa2c609Third Party Advisory
- https://github.com/aaubry/YamlDotNet#version-500Third Party Advisory
- https://github.com/aaubry/YamlDotNet/blob/f96b7cc40a0498f8bafdeb49df3aa23aa2c609Third Party Advisory
FAQ
What is CVE-2018-1000210?
CVE-2018-1000210 is a vulnerability with a CVSS score of 7.8 (HIGH). YamlDotNet version 4.3.2 and earlier contains a Insecure Direct Object Reference vulnerability in The default behavior of Deserializer.Deserialize() will deserialize user-controlled types in the line ...
How severe is CVE-2018-1000210?
CVE-2018-1000210 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2018-1000210?
Check the references section above for vendor advisories and patch information. Affected products include: Yamldotnet Project Yamldotnet.