← Back to results
Vulnerability record · public intelligence
CVE-2019-12928
CRITICAL

CVE-2019-12928

Published Jun 24, 2019 · Updated Oct 23, 2026

Severity · CVSSCRITICAL · 9.8
Known exploitationNot listed
EPSS / likelihood23.04%
QFinch risk score60 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

The QMP migrate command in QEMU version 4.0.0 and earlier is vulnerable to OS command injection, which allows the remote attacker to achieve code execution, denial of service, or information disclosure by sending a crafted QMP command to the listening server. Note: This has been disputed as a non-issue since QEMU's -qmp interface is meant to be used by trusted users. If one is able to access this interface via a tcp socket open to the internet, then it is an insecure configuration issue

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

The QMP migrate command in QEMU version 4.0.0 and earlier is vulnerable to OS command injection, which allows the remote attacker to achieve code execution, denial of service, or information disclosure by sending a crafted QMP command to the listening server. Note: This has been disputed as a non-issue since QEMU's -qmp interface is meant to be used by trusted users. If one is able to access this interface via a tcp socket open to the internet, then it is an insecure configuration issue

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSSMETASPLOIT
SSVC priority
IMMEDIATE
Confidence
60%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. fakhrizulkifli.github.io ↗

Record history

Published Jun 24, 2019 · Last refreshed Oct 23, 2026