Snakeyaml vulnerabilitiesRanked by how likely they are to be used.
Snakeyaml is made by Snakeyaml Project. We track 8 published vulnerabilities in it, across 33 versions. None of them is on the list of flaws known to be exploited today. If you run Snakeyaml, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Snakeyaml vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Snakeyaml's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Snakeyaml flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%CVE-2022-1471High
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization.
- 27%CVE-2017-18640High
The Alias feature in SnakeYAML before 1.26 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
- 2.7%CVE-2022-25857High
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.
- 2.5%CVE-2022-38752Medium
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS).
- 2.1%CVE-2022-38749Medium
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS).
- 1.9%CVE-2022-38751Medium
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS).
- 1.5%CVE-2022-41854Medium
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS).
- 1.3%CVE-2022-38750Medium
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS).
Running Snakeyaml? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.
- Matched to
- Snakeyaml on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Snakeyaml, across 33 versions.
None of Snakeyaml's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Snakeyaml. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.