{"answers":{"affected":"4 open source packages ship an affected version, including YamlDotNet and YamlDotNet.Signed. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000210 in the wild and no public exploit code.","fix":"Upgrade YamlDotNet to 5.0.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2018-1000210 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2018-1000210 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- YamlDotNet (NuGet): affected all versions; fixed in 5.0.0\n- YamlDotNet (NuGet): affected all versions; fixed in 5.0.0\n- YamlDotNet.Signed (NuGet): affected all versions; fixed in 5.0.0\n- YamlDotNet.Signed (NuGet): affected all versions; fixed in 5.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-1000210/ (Markdown: https://insights.sbomify.com/CVE-2018-1000210/index.md)","id":"CVE-2018-1000210","markdown":"https://insights.sbomify.com/CVE-2018-1000210/index.md","name":"CVE-2018-1000210","record":{"aliases":["GHSA-rpch-cqj9-h65r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"YAML parsing library","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking applications into parsing malicious YAML files using vulnerable YamlDotNet versions.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yamldotnet","vendor":"yamldotnet_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"High severity vulnerability that affects YamlDotNet and YamlDotNet.Signed","id":"CVE-2018-1000210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"deserialization","year":"2018"},"n_packages":4,"n_references":2,"next":{"headline":"Doorkeeper subject to Incorrect Permission Assignment","id":"CVE-2018-1000211"},"packages":[{"ecosystem":"NuGet","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"YamlDotNet","purl":null,"source":"GHSA-rpch-cqj9-h65r"},{"ecosystem":"NuGet","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"YamlDotNet","purl":"pkg:nuget/YamlDotNet","source":"GHSA-rpch-cqj9-h65r"},{"ecosystem":"NuGet","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"YamlDotNet.Signed","purl":null,"source":"GHSA-rpch-cqj9-h65r"},{"ecosystem":"NuGet","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"YamlDotNet.Signed","purl":"pkg:nuget/YamlDotNet.Signed","source":"GHSA-rpch-cqj9-h65r"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2018-1000209"},"products":["n/a"],"published":"2018-07-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by tricking applications into parsing malicious YAML files using vulnerable YamlDotNet versions.","url":"https://insights.sbomify.com/CVE-2018-1000210/"}