Vulnerabilities in pkg:nuget/YamlDotNet.Signed
PACKAGECVE-2018-1000210 is a HIGH (CVSS 7.8) high severity vulnerability that affects vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting YamlDotNet libraries in the NuGet ecosystem. The issue involves high severity vulnerability that affects yamldotnet and yamldotnet.signed. Remediation is available by upgrading affected packages to version 5.0.0.
pkg:nuget/YamlDotNet.Signed
Vulnerability advisories affecting package pkg:nuget/YamlDotNet.Signed. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-rpch-cqj9-h65r | CVE-2018-1000210 | HIGH | High severity vulnerability that affects YamlDotNet and YamlDotNet.Signed |
CVE-2018-1000210 at a Glance
Security Impact
CVSS: 7.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
How to Fix CVE-2018-1000210
To remediate this vulnerability, upgrade all affected YamlDotNet dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade YamlDotNet to 5.0.0
Upgrade YamlDotNet.Signed to 5.0.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for YamlDotNet
How to Check if You Are Affected
To determine whether your application is affected by CVE-2018-1000210, inspect your project dependencies for YamlDotNet:
inspect dependencies for YamlDotNet
Analyze the terminal output to locate any version of YamlDotNet in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In YamlDotNet, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2018-1000210 Affected YamlDotNet Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
YamlDotNet
|
NuGet |
< 5.0.0
|
5.0.0
|
|
YamlDotNet.Signed
|
NuGet |
< 5.0.0
|
5.0.0
|
References
Frequently Asked Questions
What is CVE-2018-1000210?
Which YamlDotNet versions are affected?
What version fixes CVE-2018-1000210?
Is YamlDotNet affected?
Is YamlDotNet.Signed affected?
What is the CVSS score of CVE-2018-1000210?
What CWE is associated with CVE-2018-1000210?
How can I check NuGet dependencies for CVE-2018-1000210?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rpch-cqj9-h65r",
"modified" : "2021-09-17T19:23:01Z",
"published" : "2018-10-16T17:01:10Z",
"aliases" : [ "CVE-2018-1000210" ],
"summary" : "High severity vulnerability that affects YamlDotNet and YamlDotNet.Signed",
"details" : "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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "NuGet",
"name" : "YamlDotNet"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.0.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.3.2"
}
}, {
"package" : {
"ecosystem" : "NuGet",
"name" : "YamlDotNet.Signed"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.0.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.3.2"
}
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-1000210"
}, {
"type" : "WEB",
"url" : "https://github.com/aaubry/YamlDotNet#version-500"
}, {
"type" : "WEB",
"url" : "https://github.com/aaubry/YamlDotNet/blob/f96b7cc40a0498f8bafdeb49df3aa23aa2c60993/YamlDotNet/Serialization/NodeTypeResolvers/TypeNameInTagNodeTypeResolver.cs#L35"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-rpch-cqj9-h65r"
}, {
"type" : "PACKAGE",
"url" : "ps://github.com/aaubry/YamlDotNet"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502", "CWE-639" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2020-06-16T21:55:19Z",
"nvd_published_at" : null
}
}