CVE-2019-6250
Last modified
CVE-2019-6250 is a vulnerability of currently unknown severity. A pointer overflow, with code execution, was discovered in ZeroMQ libzmq (aka 0MQ) 4.2.x and 4.3.x before 4.3.1. A v2_decoder.cpp zmq::v2_decoder_t::size_ready integer overflow allows an authenticated attacker to overwrite an arbitrary amount of bytes beyond the bounds of a buffer, which can be leveraged to run arbitrary code on the target system. EPSS estimates a 9.44% chance of exploitation in the next 30 days.
Description
A pointer overflow, with code execution, was discovered in ZeroMQ libzmq (aka 0MQ) 4.2.x and 4.3.x before 4.3.1. A v2_decoder.cpp zmq::v2_decoder_t::size_ready integer overflow allows an authenticated attacker to overwrite an arbitrary amount of bytes beyond the bounds of a buffer, which can be leveraged to run arbitrary code on the target system. The memory layout allows the attacker to inject OS commands into a data structure located immediately after the problematic buffer (i.e., it is not necessary to use a typical buffer-overflow exploitation technique that changes the flow of control).
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Zeromq | Libzmq | >= 4.2.0, <= 4.2.5 |
| Zeromq | Libzmq | >= 4.3.0, < 4.3.1 |
| Debian | Debian Linux | 9.0 |
References
- https://github.com/zeromq/libzmq/issues/3351Exploit, Patch, Third Party Advisory
- https://github.com/zeromq/libzmq/releases/tag/v4.3.1Third Party Advisory
- https://security.gentoo.org/glsa/201903-22Third Party Advisory
- https://www.debian.org/security/2019/dsa-4368Third Party Advisory
- https://github.com/zeromq/libzmq/issues/3351Exploit, Patch, Third Party Advisory
- https://github.com/zeromq/libzmq/releases/tag/v4.3.1Third Party Advisory
- https://security.gentoo.org/glsa/201903-22Third Party Advisory
- https://www.debian.org/security/2019/dsa-4368Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-6250?
How severe is CVE-2019-6250?
How do I fix CVE-2019-6250?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-6244An issue was discovered in UsualToolCMS 8.0. cmsadmin/a_sqlb…
- CVE-2019-6245An issue was discovered in Anti-Grain Geometry (AGG) 2.4 as …8.8
- CVE-2019-6246An issue was discovered in SVG++ (aka svgpp) 1.2.3. After ca…
- CVE-2019-6247An issue was discovered in Anti-Grain Geometry (AGG) 2.4 as …
- CVE-2019-6248PHP Scripts Mall Citysearch / Hotfrog / Gelbeseiten Clone Sc…
- CVE-2019-6249An issue was discovered in HuCart v5.7.4. There is a CSRF vu…
- CVE-2019-6251WebKitGTK and WPE WebKit prior to version 2.24.1 are vulnera…
- CVE-2019-6256A Denial of Service issue was discovered in the LIVE555 Stre…
- CVE-2019-6257A Server Side Request Forgery (SSRF) vulnerability in elFind…7.7
- CVE-2019-6258D-Link DIR-822 Rev.Bx devices with firmware v.202KRb06 and o…9.8
- CVE-2019-6259An issue was discovered in idreamsoft iCMS V7.0.13. There is…
- CVE-2019-6260The ASPEED ast2400 and ast2500 Baseband Management Controlle…
Are you affected by CVE-2019-6250?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
