CVE-2022-38750 | DoS in SnakeYAML

Exp

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.

Published: 2022-09-05 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-38750 is rated High Exploit Risk (66.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.71%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-38750

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-38750

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.15% 0.71% +0.56%
2 2026-03-04 0.08% 0.15% +0.07%
3 2025-11-21 — 0.08% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-38750

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2022-38750

GitHub Security Advisory for CVE-2022-38750

GHSA-hhhw-99gj-p3c3 · Severity: medium · Ecosystem: maven — snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write

OS Trackers for CVE-2022-38750

vendor priority summary link
debian not yet assigned CVE-2022-38750 not yet assigned priority: Debian including 1 source packages (snakeyaml), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-38750
gentoo low CVE-2022-38750: 1 GLSA(s) (202305-28), 1 atom(s) (dev-java/snakeyaml); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-38750
redhat medium — https://access.redhat.com/security/cve/CVE-2022-38750
suse high CVE-2022-38750 severity important: SUSE including 241 source package names (3.3.2-2.3:snakeyaml-1.31-150200.3.8.1, 5.0.0-beta1.2.122:snakeyaml-1.31-150200.3.8.1, …), 267 product×package rows across 33 product lines (Container containers/apache-pulsar, Container suse/manager/5.0/x86_64/server, … (33 product lines)): Known Affected 231, Fixed 36. https://www.suse.com/security/cve/CVE-2022-38750/
ubuntu medium CVE-2022-38750 medium priority: Ubuntu including 1 source packages (snakeyaml), 8 status rows across 8 suites (bionic, focal, jammy, kinetic, lunar, trusty, upstream, xenial): released 6, needs-triage 1, not-affected 1. https://ubuntu.com/security/CVE-2022-38750

Affected software / configurations for CVE-2022-38750

Vendor Product Version Raw CPE
snakeyaml_project snakeyaml < 1.31 cpe:2.3:a:snakeyaml_project:snakeyaml:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-38750

cvelogic Threat Intelligence