CVE-2017-10664

Description

qemu-nbd in QEMU (aka Quick Emulator) does not ignore SIGPIPE, which allows remote attackers to cause a denial of service (daemon crash) by disconnecting during a server-to-client reply attempt.

7.5

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 4.43% Top 15%

Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com

Affected: n/a n/a

References

Link	Tags
http://www.debian.org/security/2017/dsa-3920	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2017:2445	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2017:3473	third party advisory vendor advisory
http://www.securityfocus.com/bid/99513	third party advisory vdb entry
https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg02693.html	patch mailing list third party advisory
https://access.redhat.com/errata/RHSA-2017:3470	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2017:3472	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2017:3474	third party advisory vendor advisory
http://www.openwall.com/lists/oss-security/2017/06/29/1	patch mailing list third party advisory
https://access.redhat.com/errata/RHSA-2017:3471	third party advisory vendor advisory
https://bugzilla.redhat.com/show_bug.cgi?id=1466190	patch third party advisory issue tracking
https://access.redhat.com/errata/RHSA-2017:3466	third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2018/11/msg00038.html	third party advisory mailing list
https://access.redhat.com/errata/RHSA-2017:2390	third party advisory vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-10664?: CVE-2017-10664 has been scored as a high severity vulnerability.
How to fix CVE-2017-10664?: To fix CVE-2017-10664, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-10664 being actively exploited in the wild?: It is possible that CVE-2017-10664 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~4% probability that this vulnerability will be exploited by malicious actors in the next 30 days.