Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

yamldotnet.signed

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.8NuGetPublished

    High severity vulnerability that affects YamlDotNet and YamlDotNet.Signed

    CVE-2018-1000210 · GHSA-rpch-cqj9-h65r

    Affected
    • NuGet yamldotnet.signed <= 4.3.2
    Fixed in
    5.0.0· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 5.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →