CVE-2018-1000210 High severity vulnerability that affects YamlDotNet and YamlDotNet.Signed
Attackers can execute arbitrary code by tricking applications into parsing malicious YAML files using vulnerable YamlDotNet versions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2018-1000210?
CVE-2018-1000210 is a high-severity unsafe deserialization vulnerability in n/a, published on 13 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official 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.
Which versions are affected by CVE-2018-1000210?
4 open source packages ship an affected version, including YamlDotNet and YamlDotNet.Signed. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
YamlDotNet NuGet | All versions | 5.0.0 |
YamlDotNet NuGet | All versions | 5.0.0 |
YamlDotNet.Signed NuGet | All versions | 5.0.0 |
YamlDotNet.Signed NuGet | All versions | 5.0.0 |
Products include Yamldotnet Project Yamldotnet.
How do I fix CVE-2018-1000210?
Upgrade YamlDotNet to 5.0.0 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2018-1000210 being exploited?
There is no known exploitation of CVE-2018-1000210 in the wild and no public exploit code.
Sources
Also known as GHSA-rpch-cqj9-h65r.