CVE-2019-20175
Last modified
CVE-2019-20175 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 3.36% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Qemu | Qemu | >= 2.4.0, <= 4.2.0 |
References
- https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg01651.htmlExploit, Mailing List, Third Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg03869.htmlMailing List, Third Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-11/msg00597.htmlThird Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-11/msg02165.htmlMailing List, Patch, Third Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg01651.htmlExploit, Mailing List, Third Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg03869.htmlMailing List, Third Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-11/msg00597.htmlThird Party Advisory
- https://lists.nongnu.org/archive/html/qemu-devel/2019-11/msg02165.htmlMailing List, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-20175?
How severe is CVE-2019-20175?
How do I fix CVE-2019-20175?
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-2017In rw_t2t_handle_tlv_detect_rsp of rw_t2t_ndef.cc, there is …
- CVE-2019-20170An issue was discovered in GPAC version 0.8.0 and 0.9.0-deve…5.5
- CVE-2019-20171An issue was discovered in GPAC version 0.5.2 and 0.9.0-deve…5.5
- CVE-2019-20172Kernel/VM/MemoryManager.cpp in SerenityOS before 2019-12-30 …7.8
- CVE-2019-20173The Auth0 wp-auth0 plugin 3.11.x before 3.11.3 for WordPress…6.1
- CVE-2019-20174Auth0 Lock before 11.21.0 allows XSS when additionalSignUpFi…6.1
- CVE-2019-20176In Pure-FTPd 1.0.49, a stack exhaustion issue was discovered…7.5
- CVE-2019-20178Advisto PEEL Shopping 9.2.1 has CSRF via administrer/utilisa…6.5
- CVE-2019-20179SOPlanning 1.45 has SQL injection via the user_list.php "by"…8.8
- CVE-2019-2018In resetPasswordInternal of DevicePolicyManagerService.java,…
- CVE-2019-20180The TablePress plugin 1.9.2 for WordPress allows tablepress[…6.8
- CVE-2019-20181The awesome-support plugin 5.8.0 for WordPress allows XSS vi…4.8
Are you affected by CVE-2019-20175?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
