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
7 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
SnakeYaml's Constructor class, which inherits from SafeConstructor, allows any type be deserialized given the following line: new Yaml(new Constructor(TestDataClass.class)).load(yamlContent); Types do not have to match the types of properties in the target class. A ConstructorException is thrown, but only after a malicious payload is deserialized. Severity High, lack of type checks during deserialization allows remote code execution. Proof of Concept Execute bash run.sh. The PoC uses Constructor to deserialize a payload for RCE. RCE is demonstrated by using a payload which performs a http request to http://127.0.0.1:8000. Example output of successful run of proof of concept: Further Analysis Potential mitigations include, leveraging SnakeYaml's SafeConstructor while parsing untrusted content. See https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64581479 for discussion on the subject. Timeline Date reported: 4/11/2022 Date fixed:…
Recommended action: Upgrade to 2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
Recommended action: Upgrade to 1.32 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
Recommended action: Upgrade to 1.31 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DoS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
Recommended action: Upgrade to 1.32 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
Recommended action: Upgrade to 1.31 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections.
Recommended action: Upgrade to 1.31 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
Recommended action: Upgrade to 1.26 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.