The ne2000_receive function in hw/net/ne2000.c in QEMU before 2.4.0.1 allows attackers to cause a denial of service (infinite loop and insta
Noroxi assessment
Priority: Monitor (action score 27/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.2% (FIRST EPSS); higher than 82.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: qemu (Debian:12) 1:2.4+dfsg-3; qemu (Debian:7) 1.1.2+dfsg-6a+deb7u11; qemu-kvm (Debian:7) 1.1.2+dfsg-6+deb7u11.
Low priority for now. Upgrade to qemu (Debian:12) 1:2.4+dfsg-3; qemu (Debian:7) 1.1.2+dfsg-6a+deb7u11; qemu-kvm (Debian:7) 1.1.2+dfsg-6+deb7u11 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
The ne2000_receive function in hw/net/ne2000.c in QEMU before 2.4.0.1 allows attackers to cause a denial of service (infinite loop and instance crash) or possibly execute arbitrary code via vectors related to receiving packets.
- Published
- Jan 23, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-835
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
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 |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| arista | eos | cpe:2.3:o:arista:eos |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arista eos4.12
- arista eos4.13
- arista eos4.14
- arista eos4.15
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux15.04
- fedoraproject fedora21
- fedoraproject fedora22
- fedoraproject fedora23
- qemu qemubefore 2.4.0.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
QEMU QEMU
- before 2.4.0.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | qemu | before 1:2.4+dfsg-3 | 1:2.4+dfsg-3 |
| Debian:7 | qemu | before 1.1.2+dfsg-6a+deb7u11 | 1.1.2+dfsg-6a+deb7u11 |
| Debian:7 | qemu-kvm | before 1.1.2+dfsg-6+deb7u11 | 1.1.2+dfsg-6+deb7u11 |
| Debian:8 | qemu | before 1:2.1+dfsg-12+deb8u4 | 1:2.1+dfsg-12+deb8u4 |
| SUSE:Linux Enterprise Desktop 12 | qemu | before 2.0.2-48.9.1 | 2.0.2-48.9.1 |
| SUSE:Linux Enterprise Desktop 12 | xen | before 4.4.4_02-22.19.1 | 4.4.4_02-22.19.1 |
| SUSE:Linux Enterprise Desktop 12 SP1 | xen | before 4.5.2_06-7.1 | 4.5.2_06-7.1 |
| SUSE:Linux Enterprise Server 11 SP2-LTSS | xen | before 4.1.6_08-26.1 | 4.1.6_08-26.1 |
| SUSE:Linux Enterprise Server 11 SP3-LTSS | kvm | before 1.4.2-46.1 | 1.4.2-46.1 |
| SUSE:Linux Enterprise Server 11 SP3-LTSS | xen | before 4.2.5_20-24.9 | 4.2.5_20-24.9 |
| SUSE:Linux Enterprise Server 11 SP4 | kvm | before 1.4.2-44.1 | 1.4.2-44.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | xen | before 4.4.4_02-32.1 | 4.4.4_02-32.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 achieve46Plan
- 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
- CVE-2022-36648The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier, allows remote attackers 41Plan
- CVE-2017-16845hw/input/ps2.c in Qemu does not validate 'rptr' and 'count' values during guest migration, leading to out-of-bounds access.41Plan
- CVE-2016-7161Heap-based buffer overflow in the .receive callback of xlnx.xps-ethernetlite in QEMU (aka Quick Emulator) allows attackers to execute arbitr41Plan
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:2.4+dfsg-3 · Debian:12 | Package registry (OSV) |
| debian:qemu-kvm | 1.1.2+dfsg-6+deb7u11 · Debian:7 | Package registry (OSV) |
| suse:kvm | 1.4.2-46.1 · SUSE:Linux Enterprise Server 11 SP3-LTSS | Package registry (OSV) |
| suse:qemu | 2.0.2-48.9.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
| suse:xen | 4.5.2_06-7.1 · SUSE:Linux Enterprise Desktop 12 SP1 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 (7 more)Show less
- lists.fedoraproject.org/pipermail/package-announce/2015-October/168646.html
- lists.fedoraproject.org/pipermail/package-announce/2015-October/168671.html
- www.openwall.com/lists/oss-security/2015/09/15/2
- www.ubuntu.com/usn/USN-2745-1
- lists.gnu.org/archive/html/qemu-devel/2015-09/msg03985.html
- lists.gnu.org/archive/html/qemu-devel/2015-09/msg05832.html
- www.arista.com/en/support/advisories-notices/security-advisories/1188-security-advisory-14
Vendor advisories and official records. Exploit/PoC links are deliberately left out.