First published: Fri Jan 29 2021(Updated: )
A flaw was found in zeromq before 4.3.3. Messages with metadata are never processed by PUB sockets, but the metadata is kept referenced in the PUB object and never freed leading to memory leaks. References: <a href="https://github.com/zeromq/libzmq/pull/3935">https://github.com/zeromq/libzmq/pull/3935</a> <a href="https://github.com/zeromq/libzmq/security/advisories/GHSA-4p5v-h92w-6wxw">https://github.com/zeromq/libzmq/security/advisories/GHSA-4p5v-h92w-6wxw</a> <a href="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22344">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22344</a>
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
ZeroMQ libzmq | >=4.2.0<4.3.3 | |
redhat/zeromq | <4.3.3 | 4.3.3 |
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 for this ZeroMQ vulnerability is CVE-2021-20237.
CVE-2021-20237 has a severity rating of 7.5 (high).
CVE-2021-20237 is an uncontrolled resource consumption (memory leak) flaw that allows a remote unauthenticated attacker to send crafted messages, consuming excessive memory if the CURVE/ZAP authentication is disabled on the ZeroMQ server.
Versions before 4.3.3 of ZeroMQ are affected by CVE-2021-20237.
To fix CVE-2021-20237, upgrade ZeroMQ to version 4.3.3 or later.