YamlDotNet up to 4.3.2 Deserializer.Deserialize YAML File deserialization

Summaryinfo

A vulnerability categorized as critical has been discovered in YamlDotNet up to 4.3.2. The affected element is the function Deserializer.Deserialize. Executing a manipulation as part of YAML File can lead to deserialization. This vulnerability is tracked as CVE-2018-1000210. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in YamlDotNet up to 4.3.2. This vulnerability affects the function Deserializer.Deserialize. The manipulation as part of a YAML File leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The bug was discovered 07/11/2016. The weakness was disclosed 07/13/2018 (GitHub Repository). The advisory is available at github.com. This vulnerability was named CVE-2018-1000210 since 07/13/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 732 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• YamlDotNet

Version

• 4.3.0
• 4.3.1
• 4.3.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion