First published: Fri Sep 11 2020(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
ZeroMQ libzmq | <4.3.3 | |
Fedoraproject Fedora | =32 | |
Fedoraproject Fedora | =33 | |
Debian Debian Linux | =9.0 | |
debian/zeromq3 | 4.3.4-1+deb11u1 4.3.4-6 4.3.5-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID of this ZeroMQ vulnerability is CVE-2020-15166.
The severity of CVE-2020-15166 is high with a CVSS score of 7.5.
The affected software versions include ZeroMQ 4.3.1-4+deb10u2, 4.3.4-1, 4.3.4-6, 4.3.5-1, 4.2.5-1ubuntu0.2+, 4.3.2-2ubuntu1.20.04.1~, 4.1.4-7ubuntu0.1+, 4.3.3-1, and 4.0.4+dfsg-2ubuntu0.1+.
This vulnerability impacts users with TCP transport public endpoints, even with CURVE/ZAP enabled, by causing a denial-of-service.
Additional information about CVE-2020-15166 can be found at the following references: [link1](https://github.com/zeromq/libzmq/security/advisories/GHSA-25wp-cf8g-938m), [link2](https://github.com/zeromq/libzmq/pull/3913), [link3](https://github.com/zeromq/libzmq/pull/3973).