Skip to content

snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write

Moderate severity GitHub Reviewed Published Sep 6, 2022 to the GitHub Advisory Database • Updated Mar 15, 2024

Package

maven be.cylab:snakeyaml (Maven)

Affected versions

= 1.25.1

Patched versions

None
maven com.alipay.sofa.acts:acts-common-util (Maven)
= 1.0.0
None
maven io.prometheus.jmx:jmx_prometheus_httpserver (Maven)
= 0.17.0
None
maven io.prometheus.jmx:jmx_prometheus_httpserver_java6 (Maven)
<= 0.18.0
None
maven org.testifyproject.external:external-snakeyaml (Maven)
<= 1.0.6
None
maven org.yaml:snakeyaml (Maven)
< 1.31
1.31
maven pl.droidsonroids.yaml:snakeyaml (Maven)
<= 1.18.2
None

Description

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.

References

Published by the National Vulnerability Database Sep 5, 2022
Published to the GitHub Advisory Database Sep 6, 2022
Reviewed Sep 15, 2022
Last updated Mar 15, 2024

Severity

Moderate

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
Low
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:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.211%
(59th percentile)

Weaknesses

CVE ID

CVE-2022-38749

GHSA ID

GHSA-c4r9-r8fh-9vj2

Source code

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