Uncontrolled Resource Consumption in snakeyamlGHSA-3mc7-4q67-w48m
HIGHFix: snakeyaml/snakeyaml@fc30078GHSA-3mc7-4q67-w48m is a high-severity (CVSS 7.5) CWE-776 vulnerability in org.yaml:snakeyaml. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.yaml:snakeyaml — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.yaml:snakeyamlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.yaml:snakeyaml | all versions | 1.31org.yaml:snakeyaml:1.31 |
Affected Products
debian linuxdebiansnakeyamlsnakeyaml_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.yaml:snakeyaml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.yaml:snakeyaml to 1.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mc7-4q67-w48m is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
For RHEL-8 it's downgraded to moderate because "snakeyaml" itself in RHEL 8 or RHEL-9 isn't shipped and "prometheus-jmx-exporter" is needed as build dependency. And it's not directly exploitable, hence severity marked as moderate. Red Hat Integration and AMQ products are not vulnerable to this flaw, so their severity…
| Product | Fixed in | Advisory |
|---|---|---|
| OCP-Tools-4.12-RHEL-8 | jenkins-2-plugins-0:4.12.1698294000-1.el8 | RHSA-2023:6172 |
| OCP-Tools-4.12-RHEL-8 | jenkins-2-plugins-0:4.12.1706515741-1.el8 | RHSA-2024:0778 |
| OCP-Tools-4.13-RHEL-8 | jenkins-2-plugins-0:4.13.1698292274-1.el8 | RHSA-2023:6179 |
| OCP-Tools-4.13-RHEL-8 | jenkins-2-plugins-0:4.13.1706516346-1.el8 | RHSA-2024:0776 |
| OCP-Tools-4.14-RHEL-8 | jenkins-2-plugins-0:4.14.1699356715-1.el8 | RHSA-2023:7288 |
| OCP-Tools-4.14-RHEL-8 | jenkins-2-plugins-0:4.14.1706516441-1.el8 | RHSA-2024:0777 |
| OpenShift Developer Tools and Services for OCP 4.11 | jenkins-2-plugins-0:4.11.1683009941-1.el8 | RHSA-2023:3198 |
| Red Hat AMQ Broker 7 | snakeyaml | RHSA-2022:8876 |
Frequently Asked Questions
Is GHSA-3mc7-4q67-w48m in your dependencies?
Find it across Maven, including transitive dependencies.