CVE-2016-0749: Buffer Overflow

Published Jun 9, 2016
·
Updated

The smartcard interaction in SPICE allows remote attackers to cause a denial of service (QEMU-KVM process crash) or possibly execute arbitrary code via vectors related to connecting to a guest VM, which triggers a heap-based buffer overflow.

Affected Software

18 affected components
openSUSE Leap=42.1
openSUSE openSUSE=13.2
Debian Debian Linux=8.0
redhat Enterprise Linux=6.0
redhat Enterprise Linux=6.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
Microsoft Windows
redhat Enterprise Linux=7.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Hpc Node Eus=7.2
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.2
redhat Enterprise Linux Server Eus=7.2
redhat Enterprise Linux Workstation=7.0
Spice Project Spice

Event History

Jun 9, 2016
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-0749?

CVE-2016-0749 has a high severity due to its potential to cause a denial of service and execute arbitrary code.

2

How do I fix CVE-2016-0749?

To fix CVE-2016-0749, update your SPICE package to the latest version provided by your operating system vendor.

3

What systems are affected by CVE-2016-0749?

CVE-2016-0749 affects multiple operating systems including openSUSE Leap 42.1, openSUSE 13.2, Debian 8.0, and various versions of Red Hat Enterprise Linux.

4

What type of vulnerability is CVE-2016-0749?

CVE-2016-0749 is classified as a heap-based buffer overflow vulnerability.

5

Can CVE-2016-0749 lead to remote code execution?

Yes, CVE-2016-0749 can potentially allow remote attackers to execute arbitrary code.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203