Denial-of-Service Vulnerability in ZeroMQ

zeromq Updated 02 Oct 2025

Summary

11/09/2020
N/A
Yes i
High
7.5

CVE-2020-15166: In ZeroMQ before version 4.3.3, there is a denial-of-service vulnerability. Affects zeromq across 2 version ranges.

< 4.3.3-r0 < 04f5bbedee58c538934374dc45182d8fc5926fa3

Fixed in 4.3.3-r0. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ZeroMQ is an open-source messaging library that allows applications to connect and exchange messages in a distributed system. It provides high-performance asynchronous communication between processes, threads, and nodes. ZeroMQ supports various transport protocols, including TCP. The vulnerability affects ZeroMQ versions before 4.3.3.

Vulnerability Detail

The vulnerability, identified as CVE-2020-15166, is a denial-of-service (DoS) issue. It impacts users with TCP transport public endpoints, even if CURVE/ZAP (ZeroMQ security mechanisms) are enabled. When a raw TCP socket is opened and connected to a fully configured CURVE/ZAP endpoint, legitimate clients are unable to exchange any messages. Handshakes are successful, and messages are delivered to the library, but the server application does not receive them. This vulnerability can disrupt communication and potentially lead to service unavailability.

How To Fix

Minimum fixed version

4.3.3-r0

This is the first release that contains the fix.

sudo apk add --upgrade zeromq

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. Updating to the patched version is the recommended solution.

Conclusion

The denial-of-service vulnerability in ZeroMQ can disrupt communication between clients and the server application. It is crucial to update ZeroMQ to version 4.3.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for zeromq →

Share this vulnerability

FAQ

ZeroMQ is an open-source messaging library that enables high-performance asynchronous communication between processes, threads, and nodes in a distributed system.

The vulnerability can cause a denial-of-service condition, preventing legitimate clients from exchanging messages with the server application.

ZeroMQ versions before 4.3.3 are affected by this vulnerability.

No, there is no known workaround for this vulnerability. Updating to the patched version is recommended.

To fix this vulnerability, update ZeroMQ to version 4.3.3 or later.

Related vulnerabilities

Recent vulnerabilities recorded for zeromq.

How To Fix

Minimum fixed version

4.3.3-r0

This is the first release that contains the fix.

sudo apk add --upgrade zeromq

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