In ZeroMQ libzmq before 4.0.9, 4.1.x before 4.1.7, and 4.2.x before 4.3.2, a remote, unauthenticated client connecting to a libzmq application, running with a socket listening with CURVE encryption/authentication enabled, may cause a stack overflow and overwrite the stack with arbitrary data, due to a buffer overflow in the library. Users running public servers with the above configuration are highly encouraged to upgrade as soon as possible, as there are no known mitigations.

The remote Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4920-1 advisory.

  - In ZeroMQ libzmq before 4.0.9, 4.1.x before 4.1.7, and 4.2.x before 4.3.2, a remote, unauthenticated     client connecting to a libzmq application, running with a socket listening with CURVE     encryption/authentication enabled, may cause a stack overflow and overwrite the stack with arbitrary data,     due to a buffer overflow in the library. Users running public servers with the above configuration are     highly encouraged to upgrade as soon as possible, as there are no known mitigations. (CVE-2019-13132)

  - In ZeroMQ before version 4.3.3, there is a denial-of-service vulnerability. Users with TCP transport     public endpoints, even with CURVE/ZAP enabled, are impacted. If a raw TCP socket is opened and connected     to an endpoint that is fully configured with CURVE/ZAP, legitimate clients will not be able to exchange     any message. Handshakes complete successfully, and messages are delivered to the library, but the server     application never receives them. This is patched in version 4.3.3. (CVE-2020-15166)

  - An uncontrolled resource consumption (memory leak) flaw was found in the ZeroMQ client in versions before     4.3.3 in src/pipe.cpp. This issue causes a client that connects to multiple malicious or compromised     servers to crash. The highest threat from this vulnerability is to system availability. (CVE-2021-20234)

  - There's a flaw in the zeromq server in versions before 4.3.3 in src/decoder_allocators.hpp. The decoder     static allocator could have its sized changed, but the buffer would remain the same as it is a static     buffer. A remote, unauthenticated attacker who sends a crafted request to the zeromq server could trigger     a buffer overflow WRITE of arbitrary data if CURVE/ZAP authentication is not enabled. The greatest impact     of this flaw is to application availability, data integrity, and confidentiality. (CVE-2021-20235)

  - An uncontrolled resource consumption (memory leak) flaw was found in ZeroMQ's src/xpub.cpp in versions     before 4.3.3. This flaw allows a remote unauthenticated attacker to send crafted PUB messages that consume     excessive memory if the CURVE/ZAP authentication is disabled on the server, causing a denial of service.
    The highest threat from this vulnerability is to system availability. (CVE-2021-20237)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES11 host has a package installed that is affected by a vulnerability as referenced in the SUSE- SU-2019:14117-1 advisory.

  - In ZeroMQ libzmq before 4.0.9, 4.1.x before 4.1.7, and 4.2.x before 4.3.2, a remote, unauthenticated     client connecting to a libzmq application, running with a socket listening with CURVE     encryption/authentication enabled, may cause a stack overflow and overwrite the stack with arbitrary data,     due to a buffer overflow in the library. Users running public servers with the above configuration are     highly encouraged to upgrade as soon as possible, as there are no known mitigations. (CVE-2019-13132)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Fang-Pen Lin reports :

A remote, unauthenticated client connecting to a libzmq application, running with a socket listening with CURVE encryption/authentication enabled, may cause a stack overflow and overwrite the stack with arbitrary data, due to a buffer overflow in the library. Users running public servers with the above configuration are highly encouraged to upgrade as soon as possible, as there are no known mitigations.

Security fix for CVE-2019-13132

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An update of the zeromq package has been released.

The remote host is affected by the vulnerability described in GLSA-201908-17 (ZeroMQ: Arbitrary code execution)

    A buffer overflow was discovered in ZeroMQ.
  Impact :

    An attacker could possibly execute arbitrary code with the privileges of       the process or cause a Denial of Service condition.
  Workaround :

    There is no known workaround at this time.

This update for zeromq fixes the following issues :

  - CVE-2019-13132: An unauthenticated remote attacker could     have exploited a stack overflow vulnerability on a     server that is supposed to be protected by encryption     and authentication to potentially gain a remote code     execution. (bsc#1140255)

  - Correctly mark license files as licence instead of     documentation (bsc#1082318)

This update was imported from the SUSE:SLE-15:Update update project.

This update for zeromq fixes the following issues :

  - CVE-2019-13132: An unauthenticated remote attacker could     have exploited a stack overflow vulnerability on a     server that is supposed to be protected by encryption     and authentication to potentially gain a remote code     execution. (bsc#1140255)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

It was discovered that ZeroMQ incorrectly handled certain application metadata. A remote attacker could use this issue to cause ZeroMQ to crash, or possibly execute arbitrary code.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for zeromq fixes the following issues :

CVE-2019-13132: An unauthenticated remote attacker could have exploited a stack overflow vulnerability on a server that is supposed to be protected by encryption and authentication to potentially gain a remote code execution. (bsc#1140255)

Correctly mark license files as licence instead of documentation (bsc#1082318)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Fang-Pen Lin discovered a stack-based buffer-overflow flaw in ZeroMQ, a lightweight messaging kernel library. A remote, unauthenticated client connecting to an application using the libzmq library, running with a socket listening with CURVE encryption/authentication enabled, can take advantage of this flaw to cause a denial of service or the execution of arbitrary code.

Fang-Pen Lin discovered a stack-based buffer-overflow flaw in ZeroMQ, a lightweight messaging kernel library. A remote, unauthenticated client connecting to an application using the libzmq library, running with a socket listening with CURVE encryption/authentication enabled, can take advantage of this flaw to cause a denial of service or the execution of arbitrary code.

For Debian 8 'Jessie', this problem has been fixed in version 4.0.5+dfsg-2+deb8u2.

We recommend that you upgrade your zeromq3 packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
183116	Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM : ZeroMQ vulnerabilities (USN-4920-1)	Nessus	Ubuntu Local Security Checks	critical
150684	SUSE SLES11 Security Update : zeromq (SUSE-SU-2019:14117-1)	Nessus	SuSE Local Security Checks	critical
149977	FreeBSD : libzmq4 -- Stack overflow (6954a2b0-bda8-11eb-a04e-641c67a117d8)	Nessus	FreeBSD Local Security Checks	critical
129649	Fedora 31 : zeromq (2019-d20ce4d5a1)	Nessus	Fedora Local Security Checks	critical
129543	Fedora 30 : zeromq (2019-8916b4e890)	Nessus	Fedora Local Security Checks	critical
129541	Fedora 29 : zeromq (2019-4d8f9a9235)	Nessus	Fedora Local Security Checks	critical
128723	Photon OS 2.0: Zeromq PHSA-2019-2.0-0171	Nessus	PhotonOS Local Security Checks	critical
128167	Photon OS 1.0: Zeromq PHSA-2019-1.0-0245	Nessus	PhotonOS Local Security Checks	critical
128162	Photon OS 3.0: Zeromq PHSA-2019-3.0-0024	Nessus	PhotonOS Local Security Checks	critical
127966	GLSA-201908-17 : ZeroMQ: Arbitrary code execution	Nessus	Gentoo Local Security Checks	critical
126902	openSUSE Security Update : zeromq (openSUSE-2019-1767)	Nessus	SuSE Local Security Checks	critical
126596	SUSE SLED12 Security Update : zeromq (SUSE-SU-2019:1785-1)	Nessus	SuSE Local Security Checks	critical
126566	Ubuntu 16.04 LTS / 18.04 LTS : ZeroMQ vulnerability (USN-4050-1)	Nessus	Ubuntu Local Security Checks	critical
126562	SUSE SLED15 / SLES15 Security Update : zeromq (SUSE-SU-2019:1776-1)	Nessus	SuSE Local Security Checks	critical
126529	Debian DSA-4477-1 : zeromq3 - security update	Nessus	Debian Local Security Checks	critical
126528	Debian DLA-1849-1 : zeromq3 security update	Nessus	Debian Local Security Checks	critical

Detections

Analytics

CVE-2019-13132

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical