Auth bypass in Yamldotnet Project
CVE-2018-1000210
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.
Vulnerability class: Insecure Deserialization
EPSS: 0.015 (71.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Affected products
- Yamldotnet_project Yamldotnet
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (x_refsource_CONFIRM, Third Party Advisory)
- cve@mitre.org (x_refsource_CONFIRM, Third Party Advisory)
Frequently asked questions
- What is CVE-2018-1000210?
- CVE-2018-1000210 is a high-severity vulnerability in Yamldotnet Project, classified under Deserialization of Untrusted Data. CVSS score: 7.8/10. Published 2018-07-13.
- How severe is CVE-2018-1000210?
- High severity. CVSS v3 base score is 7.8 out of 10.
- Is CVE-2018-1000210 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.