Critical Pointer Overflow Vulnerability in ZeroMQ Package

zeromq Updated 02 Oct 2025

Summary

13/01/2019
N/A
Yes i
High
8.8

ALPINE-CVE-2019-6250: A pointer overflow, with code execution, was discovered in ZeroMQ libzmq (aka 0MQ) 4.2.x and 4.3.x before 4.3.1. Affects zeromq versions < 4.3.1-r0. Fixed in 4.3.1-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 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

ZeroMQ is a high-performance asynchronous messaging library aimed at use in scalable distributed or concurrent applications. It provides a message queue, but unlike traditional message brokers, it can be used in a variety of messaging patterns such as publish-subscribe, request-reply, and more. The library is widely used in various applications for its efficiency and flexibility. However, it has been found to be vulnerable to a pointer overflow issue that can lead to severe security risks.

Vulnerability Detail

A pointer overflow vulnerability exists in ZeroMQ libzmq (also known as 0MQ) versions 4.2.x and 4.3.x prior to 4.3.1. This vulnerability arises from an integer overflow in the v2_decoder.cpp file, specifically in the zmq::v2_decoder_t::size_ready function. An authenticated attacker can exploit this flaw to overwrite an arbitrary amount of bytes beyond the bounds of a buffer, potentially allowing them to execute arbitrary code on the target system. This vulnerability is particularly dangerous as it allows attackers to inject OS commands into a data structure located immediately after the problematic buffer, bypassing traditional buffer-overflow exploitation techniques.

How To Fix

Minimum fixed version

4.3.1-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

If immediate updating is not feasible, consider implementing network-level controls to restrict access to the ZeroMQ service, thereby limiting the potential for exploitation until the package can be updated.

Conclusion

In summary, the pointer overflow vulnerability in ZeroMQ poses a significant risk to systems using affected versions of the library. It is essential to update to the patched version 4.3.1-r0 or later to mitigate this risk. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert, which can provide real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for zeromq →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 8.8, indicating a high severity level.

The affected versions are ZeroMQ libzmq 4.2.x and 4.3.x prior to 4.3.1.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Exploitation of this vulnerability can lead to arbitrary code execution, allowing attackers to gain control over the affected system.

Yes, you can implement network-level controls to restrict access to the ZeroMQ service as a temporary measure.

Related vulnerabilities

Recent vulnerabilities recorded for zeromq.

How To Fix

Minimum fixed version

4.3.1-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