CVE-2015-6855

HIGHCVSS 7.5/10EPSS 3.50%

Last modified

CVE-2015-6855 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. hw/ide/core.c in QEMU does not properly restrict the commands accepted by an ATAPI device, which allows guest users to cause a denial of service or possibly have unspecified other impact via certain IDE commands, as demonstrated by a WIN_READ_NATIVE_MAX command to an empty drive, which triggers a divide-by-zero error and instance crash.. EPSS estimates a 3.50% chance of exploitation in the next 30 days.

Description

hw/ide/core.c in QEMU does not properly restrict the commands accepted by an ATAPI device, which allows guest users to cause a denial of service or possibly have unspecified other impact via certain IDE commands, as demonstrated by a WIN_READ_NATIVE_MAX command to an empty drive, which triggers a divide-by-zero error and instance crash.

Metrics

CVSS 3.1
7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS Probability
3.50%

87.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
QemuQemu<= 2.4.1
DebianDebian Linux7.0
DebianDebian Linux8.0
DebianDebian Linux9.0
FedoraprojectFedora21
FedoraprojectFedora22
FedoraprojectFedora23
SuseLinux Enterprise Desktop12
SuseLinux Enterprise Server12
CanonicalUbuntu Linux12.04
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux15.04
AristaEosAll versions

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2015-6855?
hw/ide/core.c in QEMU does not properly restrict the commands accepted by an ATAPI device, which allows guest users to cause a denial of service or possibly have unspecified other impact via certain IDE commands, as demonstrated by a WIN_READ_NATIVE_MAX command to an empty drive, which triggers a divide-by-zero error and instance crash.
How severe is CVE-2015-6855?
CVE-2015-6855 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 3.50% probability of exploitation in the next 30 days.
How do I fix CVE-2015-6855?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2015-6855?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST