Auth bypass in Yamldotnet Project
CVE-2018-1000210
- CVSS v3
- 7.8 High
- Public exploits
- None known
- EPSS
- 0.015 · 74.3th percentile
- Published
- 2018-07-13
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
Published · last modified .
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.
- Attack Vector
- Local
AV:L - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- Required
UI:R - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.015, 74.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/aaubry/YamlDotNet (Third Party Advisory)
- github.com/aaubry/YamlDotNet/blob/f96b7cc40a0498f8bafdeb49df3aa23aa2c60993/Yaml… (Third Party Advisory)