CVE-2020-1711
No exploitation reported by the sources we read.
- Published2020-02-11
- WeaknessCWE-122 · CWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
An out-of-bounds heap buffer access flaw was found in the way the iSCSI Block driver in QEMU versions 2.12.0 before 4.2.1 handled a response coming from an iSCSI server while checking the status of a Logical Address Block (LBA) in an iscsi_co_block_status() routine. A remote user could use this flaw to crash the QEMU process, resulting in a denial of service or potential execution of arbitrary code with privileges of the QEMU process on the host.
Timeline
dates in UTC- 2020-02-1120:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-1711?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-1711?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | = 7.0 | no fix published | NVD |
| 8.0 | = 8.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 10.x | = 10 | no fix published | NVD |
| 13.x | = 13 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- libiscsiAlmaLinux:8all versions · fixed in 1.18.0-8.module_el8.3.0+2048+e7a0a3eaand 2 other packages
- libiscsiAlmaLinux:8all versions · fixed in 1.18.0-8.module_el8.5.0+2608+72063365and 2 other packages
- libiscsiAlmaLinux:8all versions · fixed in 1.18.0-8.module_el8.6.0+2880+7d9e3703and 2 other packages
- netcfAlmaLinux:8all versions · fixed in 0.2.8-12.module_el8.3.0+2048+e7a0a3eaand 2 other packages
- netcfAlmaLinux:8all versions · fixed in 0.2.8-12.module_el8.5.0+2608+72063365and 2 other packages
- netcfAlmaLinux:8all versions · fixed in 0.2.8-12.module_el8.6.0+2880+7d9e3703and 2 other packages
- sgabiosAlmaLinux:8all versions · fixed in 1:0.20170427git-3.module_el8.3.0+2048+e7a0a3ea
- sgabiosAlmaLinux:8all versions · fixed in 1:0.20170427git-3.module_el8.5.0+2608+72063365and 1 other package
1 more package range on OSV.dev
Fix
Advisories and patches
- bugzilla.redhat.comPatch
- lists.gnu.orgPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
- Published
- 2020-02-11
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-1711?
Is CVE-2020-1711 actively exploited?
What is the CVSS score for CVE-2020-1711?
Running netcf? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.