QEMU up to 4.2.0 hw/ide/core.c ide_dma_cb unusual condition ⚔ [Disputed]

Summaryinfo

A vulnerability, which was classified as problematic, was found in QEMU up to 4.2.0. Affected by this issue is the function ide_dma_cb of the file hw/ide/core.c. Executing a manipulation can lead to unusual condition. This vulnerability is registered as CVE-2019-20175. It is possible to launch the attack remotely. No exploit is available. The existence of this vulnerability is still disputed at present.

Detailsinfo

A vulnerability was found in QEMU up to 4.2.0 (Virtualization Software). It has been declared as problematic. This vulnerability affects the function ide_dma_cb of the file hw/ide/core.c. The manipulation with an unknown input leads to a unusual condition vulnerability. The CWE definition for the vulnerability is CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. As an impact it is known to affect availability. CVE summarizes:

** DISPUTED ** An issue was discovered in ide_dma_cb() in hw/ide/core.c in QEMU 2.4.0 through 4.2.0. The guest system can crash the QEMU process in the host system via a special SCSI_IOCTL_SEND_COMMAND. It hits an assertion that implies that the size of successful DMA transfers there must be a multiple of 512 (the size of a sector). NOTE: a member of the QEMU security team disputes the significance of this issue because a "privileged guest user has many ways to cause similar DoS effect, without triggering this assert."

The weakness was published 12/31/2019. This vulnerability was named CVE-2019-20175 since 12/31/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/27/2024).

The real existence of this vulnerability is still doubted at the moment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Virtualization Software

Name

• QEMU

Version

• 4.0
• 4.1
• 4.2.0

License

• open-source

Website

• Product: https://www.qemu.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion