Security readout for executives and security teams
This flaw affects older QEMU virtualization hosts using Cirrus VGA emulation. A privileged user inside a guest VM could crash the QEMU process and may execute code on the host as the QEMU process. The main business risk is tenant-to-host impact on legacy virtualization infrastructure. Exposure is most likely on legacy QEMU-based hosts or downstream virtualization packages that still include affected Cirrus VGA emulation. Risk is higher where untrusted or semi-trusted users can obtain privileged control inside guest VMs. Treat as a legacy virtualization containment risk. It is not marked as actively exploited in the provided sources, but affected shared hosts should be patched because the impact may reach the host process from inside a VM. Mitigation focus: Upgrade QEMU or downstream virtualization packages using vendor security advisories.; Confirm whether QEMU is older than 2.8 on virtualization hosts.; Disable or avoid Cirrus VGA emulation where vendor-supported alternatives exist..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-2620 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L1.33.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.5MediumVector: CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- [debian-lts-announce] 20180906 [SECURITY] [DLA 1497-1] qemu security updateCVE reference · mailing-list, x_refsource_MLIST
- https://xenbits.xen.org/xsa/advisory-209.htmlCVE reference · x_refsource_CONFIRM
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2620CVE reference · x_refsource_CONFIRM
- [debian-lts-announce] 20180206 [SECURITY] [DLA 1270-1] xen security updateCVE reference · mailing-list, x_refsource_MLIST
- GLSA-201704-01CVE reference · vendor-advisory, x_refsource_GENTOO
- [qemu-devel] 20170221 [PATCH] cirrus: add blit_is_unsafe call to cirrus_bitblt_cputovideo (CVE-2017-2620)CVE reference · mailing-list, x_refsource_MLIST
- https://support.citrix.com/article/CTX220771CVE reference · x_refsource_CONFIRM
- GLSA-201703-07CVE reference · vendor-advisory, x_refsource_GENTOO
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
