Skip to content

Uncontrolled Resource Consumption in snakeyaml

High severity GitHub Reviewed Published Aug 31, 2022 to the GitHub Advisory Database • Updated Mar 15, 2024

Package

maven org.yaml:snakeyaml (Maven)

Affected versions

< 1.31

Patched versions

1.31
Published by the National Vulnerability Database Aug 30, 2022
Published to the GitHub Advisory Database Aug 31, 2022
Reviewed Sep 9, 2022
Last updated Mar 15, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.421%
(74th percentile)

CVE ID

CVE-2022-25857

GHSA ID

GHSA-3mc7-4q67-w48m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.