First published: Fri Jan 29 2021(Updated: )
A flaw was found in zeromq before 4.3.3. When a pipe processes a delimiter and is already not in active state but still has an unfinished message, the message is leaked causing a crash. References: <a href="https://github.com/zeromq/libzmq/pull/3918">https://github.com/zeromq/libzmq/pull/3918</a> <a href="https://github.com/zeromq/libzmq/security/advisories/GHSA-wfr2-29gj-5w87">https://github.com/zeromq/libzmq/security/advisories/GHSA-wfr2-29gj-5w87</a> <a href="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22037">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22037</a> <a href="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22123">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22123</a>
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
ZeroMQ libzmq | <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.
CVE-2021-20234 is an uncontrolled resource consumption (memory leak) vulnerability in the ZeroMQ client.
The severity of CVE-2021-20234 is medium with a CVSS score of 6.5.
Versions before 4.3.3 of the ZeroMQ client are affected.
CVE-2021-20234 can cause a system to crash if a client connects to multiple malicious or compromised servers.
To fix CVE-2021-20234, upgrade to version 4.3.3-1 of the ZeroMQ client.