CVE-2018-11779: Deserialization of Untrusted Data in Apache Storm

org.apache.storm:storm-kafka Updated 02 Oct 2025

Summary

01/08/2019
Yes i
Critical
9.8

CVE-2018-11779: Deserialization of Untrusted Data in Apache Storm. Affects org.apache.storm:storm-kafka versions >= 1.1.0, < 1.2.3. Fixed in 1.2.3. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Storm is a distributed real-time computation system that allows users to process large streams of data in real-time. It provides a scalable and fault-tolerant platform for processing and analyzing data streams. The storm-kafka and storm-kafka-client modules are used in Apache Storm to integrate with Apache Kafka, a distributed streaming platform. These modules allow Storm to consume data from Kafka topics and process it in real-time. However, a vulnerability in these modules allows an attacker to deserialize user-provided bytes into a Java class, potentially leading to remote code execution.

Vulnerability Detail

The vulnerability exists in Apache Storm versions 1.1.0 to 1.2.2 when using the storm-kafka or storm-kafka-client modules. An attacker can exploit this vulnerability by providing malicious serialized data to the Storm UI daemon. When the deserialization process occurs, the attacker's code can be executed, leading to potential remote code execution. This can result in unauthorized access, data breaches, and other malicious activities.

How To Fix

Minimum fixed version

1.2.3

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to Apache Storm version 1.2.3 or later.

Conclusion

The deserialization vulnerability in Apache Storm can lead to remote code execution and other malicious activities. It is crucial to upgrade to the fixed version of Apache Storm and follow secure coding practices to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.storm:storm-kafka →

Share this vulnerability

FAQ

Apache Storm is a distributed real-time computation system used for processing large streams of data in real-time. It provides a scalable and fault-tolerant platform for processing and analyzing data streams.

The vulnerability affects Apache Storm versions 1.1.0 to 1.2.2.

This vulnerability allows an attacker to execute arbitrary code on the affected system, potentially leading to unauthorized access, data breaches, and other malicious activities.

To fix this vulnerability, it is recommended to upgrade to Apache Storm version 1.2.3 or later and update the dependencies to use the fixed version of the storm-kafka or storm-kafka-client modules.

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to Apache Storm version 1.2.3 or later.

How To Fix

Minimum fixed version

1.2.3

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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