CVE-2020-13765: rom_copy() in hw/core/loader.c in QEMU 4.0 and 4.1.0 does not validate the relationship between two addresses, which allows attackers to tri
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: qemu (Debian:10) 1:3.1+dfsg-8+deb10u6; qemu (Debian:12) 1:4.2-1; qemu (Debian:8) 1:2.1+dfsg-12+deb8u15.
Low priority for now. Upgrade to qemu (Debian:10) 1:3.1+dfsg-8+deb10u6; qemu (Debian:12) 1:4.2-1; qemu (Debian:8) 1:2.1+dfsg-12+deb8u15 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
rom_copy() in hw/core/loader.c in QEMU 4.0 and 4.1.0 does not validate the relationship between two addresses, which allows attackers to trigger an invalid memory copy operation.
- Published
- Jun 4, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-787
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qemu | qemu | cpe:2.3:a:qemu:qemu |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux20.04
- debian debian linux8.0
- debian debian linux9.0
- qemu qemu4.0.0
- qemu qemu4.1.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | qemu | before 1:3.1+dfsg-8+deb10u6 | 1:3.1+dfsg-8+deb10u6 |
| Debian:12 | qemu | before 1:4.2-1 | 1:4.2-1 |
| Debian:8 | qemu | before 1:2.1+dfsg-12+deb8u15 | 1:2.1+dfsg-12+deb8u15 |
| Debian:9 | qemu | before 1:2.8+dfsg-6+deb9u10 | 1:2.8+dfsg-6+deb9u10 |
| Red Hat:enterprise_linux:7::client | qemu-img | before 10:1.5.3-175.el7_9.3 | 10:1.5.3-175.el7_9.3 |
| Red Hat:enterprise_linux:7::client | qemu-kvm | before 10:1.5.3-175.el7_9.3 | 10:1.5.3-175.el7_9.3 |
| Red Hat:enterprise_linux:7::client | qemu-kvm-common | before 10:1.5.3-175.el7_9.3 | 10:1.5.3-175.el7_9.3 |
| Red Hat:enterprise_linux:7::client | qemu-kvm-debuginfo | before 10:1.5.3-175.el7_9.3 | 10:1.5.3-175.el7_9.3 |
| Red Hat:enterprise_linux:7::client | qemu-kvm-tools | before 10:1.5.3-175.el7_9.3 | 10:1.5.3-175.el7_9.3 |
| SUSE:HPE Helion OpenStack 8 | qemu | before 2.9.1-6.47.1 | 2.9.1-6.47.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | qemu | before 3.1.1.1-9.24.3 | 3.1.1.1-9.24.3 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | qemu | before 2.11.2-9.43.1 | 2.11.2-9.43.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | kvm | before 1.4.2-53.38.1 | 1.4.2-53.38.1 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | kvm | before 1.4.2-60.34.1 | 1.4.2-60.34.1 |
| SUSE:Linux Enterprise Server 12 SP2-BCL | qemu | before 2.6.2-41.62.1 | 2.6.2-41.62.1 |
| SUSE:Linux Enterprise Server 12 SP5 | qemu | before 3.1.1.1-48.2 | 3.1.1.1-48.2 |
| SUSE:OpenStack Cloud 9 | qemu | before 2.11.2-5.29.1 | 2.11.2-5.29.1 |
Same product
qemu: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-12928The QMP migrate command in QEMU version 4.0.0 and earlier is vulnerable to OS command injection, which allows the remote attacker to achieve60This week
- CVE-2015-8556Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.44Plan
- CVE-2017-15118A stack-based buffer overflow vulnerability was found in NBD server implementation in qemu before 2.11 allowing a client to request an expor43Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-13659Jun 2, 2020 · address_space_map in exec.c in QEMU 4.2.0 can trigger a NULL pointer dereference related to BounceBuffer.10Monitor
- ← EarlierCVE-2020-13754Jun 2, 2020 · hw/pci/msix.c in QEMU 4.2.0 allows guest OS users to trigger an out-of-bounds access via a crafted address in an msi-x mmio operation.26Monitor
- Later →CVE-2020-13791Jun 4, 2020 · hw/pci/pci.c in QEMU 4.2.0 allows guest OS users to trigger an out-of-bounds access by providing an address near the end of the PCI configur22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:qemu | 1:4.2-1 · Debian:12 | Package registry (OSV) |
| red hat:qemu-img | 10:1.5.3-175.el7_9.3 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:qemu-kvm | 10:1.5.3-175.el7_9.3 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:qemu-kvm-common | 10:1.5.3-175.el7_9.3 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:qemu-kvm-debuginfo | 10:1.5.3-175.el7_9.3 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:qemu-kvm-tools | 10:1.5.3-175.el7_9.3 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:kvm | 1.4.2-60.34.1 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:qemu | 2.9.1-6.47.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/qemu/qemu/commit/4f1c6cb2f9afafda05eab150fd2bd284edce6676
- lists.debian.org/debian-lts-announce/2020/06/msg00032.html
- lists.debian.org/debian-lts-announce/2020/07/msg00020.html
- security.netapp.com/advisory/ntap-20200619-0006/
- usn.ubuntu.com/4467-1/
- www.openwall.com/lists/oss-security/2020/06/03/6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.