CVE-2017-2630
Last modified
CVE-2017-2630 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. A stack buffer overflow flaw was found in the Quick Emulator (QEMU) before 2.9 built with the Network Block Device (NBD) client support. The flaw could occur while processing server's response to a 'NBD_OPT_LIST' request. EPSS estimates a 2.65% chance of exploitation in the next 30 days.
Description
A stack buffer overflow flaw was found in the Quick Emulator (QEMU) before 2.9 built with the Network Block Device (NBD) client support. The flaw could occur while processing server's response to a 'NBD_OPT_LIST' request. A malicious NBD server could use this issue to crash a remote NBD client resulting in DoS or potentially execute arbitrary code on client host with privileges of the QEMU process.
Metrics
CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Qemu | Qemu | < 2.9 |
References
- http://www.openwall.com/lists/oss-security/2017/02/15/2Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/96265Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:2392Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2630Issue Tracking, Patch, Third Party Advisory
- https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg01246.htmlPatch, Third Party Advisory
- https://security.gentoo.org/glsa/201704-01Third Party Advisory
- http://www.openwall.com/lists/oss-security/2017/02/15/2Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/96265Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:2392Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2630Issue Tracking, Patch, Third Party Advisory
- https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg01246.htmlPatch, Third Party Advisory
- https://security.gentoo.org/glsa/201704-01Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-2630?
How severe is CVE-2017-2630?
How do I fix CVE-2017-2630?
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 2017
- CVE-2017-2624It was found that xorg-x11-server before 1.19.0 including us…5.9
- CVE-2017-2625It was discovered that libXdmcp before 1.1.2 including used …6.5
- CVE-2017-2626It was discovered that libICE before 1.0.9-8 used a weak ent…5.2
- CVE-2017-2627A flaw was found in openstack-tripleo-common as shipped with…8.2
- CVE-2017-2628curl, as shipped in Red Hat Enterprise Linux 6 before versio…
- CVE-2017-2629curl before 7.53.0 has an incorrect TLS Certificate Status R…4.3
- CVE-2017-2631Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-2632A logic error in valid_role() in CloudForms role validation …4.9
- CVE-2017-2633An out-of-bounds memory access issue was found in Quick Emul…5.4
- CVE-2017-2634It was found that the Linux kernel's Datagram Congestion Con…7.5
- CVE-2017-2635A NULL pointer deference flaw was found in the way libvirt f…7.7
- CVE-2017-2636Race condition in drivers/tty/n_hdlc.c in the Linux kernel t…7
Are you affected by CVE-2017-2630?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
