Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2021-21341 — XStream DoS CVE-2021-21341 | Kitploit
Tools/GitHubGitHub/s-index/cve-2021-21341
Vulnerability AnalysisExploitationLearning & EducationLabs & Practice
GitHubs-index/cve-2021-21341

CVE-2021-21341

XStream DoS CVE-2021-21341

View Repository
125 years agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2021-21341 XStream DoS

XStream Official Announcement

CVE-2021-21341

Vulnerability

CVE-2021-21341: XStream can cause a Denial of Service.

Affected Versions

All versions until and including version 1.4.15 are affected, if using the version out of the box. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.

Description

The processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject a manipulated ByteArrayInputStream (or derived class), that can cause an endless loop resulting in a denial of service.

Docker Demo

cve-2021-21341

Set Up XStream Environment & PoC Execution

  1. Build an image from a Dockerfile (Set Up)
root@kitploit:~
$ docker build -t cve-2021-21341 .
  1. Run java -jar xstream in a new container (PoC Execution)
root@kitploit:~
$ docker run -it --rm cve-2021-21341
Download Tool

Output

root@kitploit:~
Security framework of XStream not explicitly initialized, using predefined black list on your own risk.

(never end)

Solution

  • Update xstream version to 1.4.16 or higher

Change pom.xml to bellow

root@kitploit:~
        <dependency>
            <groupId>com.thoughtworks.xstream</groupId>
            <artifactId>xstream</artifactId>
            <version>1.4.16</version>
        </dependency>
  • Use XStream's security framework

Add NoTypePermission.NONE

root@kitploit:~
import com.thoughtworks.xstream.security.NoTypePermission; // Add

XStream xstream = new XStream();
xstream.addPermission(NoTypePermission.NONE); // Add
xstream.fromXML(xml);