Guest-triggered hang via unchecked NE2000 ring index
Published Jan 23, 2020 · Updated Aug 6, 2024
Infinite loop in QEMU before 2.4.0.1 allows guest OS users to hang an instance by sending crafted packets to an emulated NE2000 NIC. In hw/net/ne2000.c, ne2000_receive lets its local index exceed the 49,152-byte ring buffer, then repeatedly processes zero available bytes instead of leaving the receive loop. A privileged guest user must control packet reception through an enabled NE2000 device; the demonstrated consequence is a QEMU process hang.
Summary
What happened
Infinite loop in QEMU before 2.4.0.1 allows guest OS users to hang an instance by sending crafted packets to an emulated NE2000 NIC. In hw/net/ne2000.c, ne2000_receive lets its local index exceed the 49,152-byte ring buffer, then repeatedly processes zero available bytes instead of leaving the receive loop. A privileged guest user must control packet reception through an enabled NE2000 device; the demonstrated consequence is a QEMU process hang.
The record
- CVE
- CVE-2015-5278
- Published
- Jan 23, 2020
- Updated
- Aug 6, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-835, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 2.4.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo