CVE-2020-8441: Deserialization of Untrusted Data in JYaml

org.jyaml:jyaml Updated 02 Oct 2025

Summary

24/05/2022
No i
Critical
9.8

CVE-2020-8441: Deserialization of Untrusted Data in JYaml. Affects org.jyaml:jyaml versions < 1.3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

JYaml is a discontinued open-source library for Java that provides YAML parsing and serialization capabilities. It is commonly used in Maven projects. The library allows developers to load YAML data and convert it into Java objects. However, a vulnerability has been discovered in JYaml versions 0 to 1.3 that allows remote code execution during the deserialization of a malicious payload through the load() function.

Vulnerability Detail

The vulnerability, identified as CVE-2020-8441, arises from the improper handling of untrusted data during deserialization. An attacker can exploit this vulnerability by crafting a malicious payload and passing it to the load() function. When the payload is deserialized, arbitrary code can be executed on the target system, leading to potential remote code execution. This can result in unauthorized access, data breaches, and other malicious activities.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As JYaml is no longer actively maintained, there may not be an official workaround provided by the project. However, developers can mitigate the risk by implementing input validation and sanitization techniques before deserializing YAML data. This involves carefully inspecting and validating the input data to ensure it meets the expected format and does not contain any malicious content.

Conclusion

The vulnerability in JYaml versions 0 to 1.3 allows remote code execution during deserialization of a malicious payload. To mitigate the risk, it is advised to upgrade to a non-affected version or switch to an actively maintained alternative library. Implementing input validation and sanitization techniques can also help reduce the impact of this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.jyaml:jyaml →

Share this vulnerability

FAQ

JYaml is an open-source library for Java that provides YAML parsing and serialization capabilities. It allows developers to convert YAML data into Java objects.

The vulnerability allows remote code execution, which can lead to unauthorized access, data breaches, and other malicious activities on the target system.

Versions 0 to 1.3 of JYaml are affected by this vulnerability.

As JYaml is a discontinued project, it is recommended to find an alternative YAML parsing library that is actively maintained and has addressed similar vulnerabilities.

Implement input validation and sanitization techniques before deserializing YAML data. Carefully inspect and validate the input data to ensure it meets the expected format and does not contain any malicious content.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback