Network interface hang via EEPROM-triggering packet bytes
Published Feb 13, 2020 · Updated Aug 6, 2024
Denial of service in Intel 82574L controllers through 2013-02-06 allows remote attackers to halt network processing via crafted packets. An incorrectly configured EEPROM image makes the controller enter a non-processing state when it parses byte value 0x32, 0x33, or 0x34 at frame offset 0x47f. Only affected motherboard implementations are exposed; the interface hang persists across a reboot and requires a physical power cycle.
Summary
What happened
Denial of service in Intel 82574L controllers through 2013-02-06 allows remote attackers to halt network processing via crafted packets. An incorrectly configured EEPROM image makes the controller enter a non-processing state when it parses byte value 0x32, 0x33, or 0x34 at frame offset 0x47f. Only affected motherboard implementations are exposed; the interface hang persists across a reboot and requires a physical power cycle.
The record
- CVE
- CVE-2013-1634
- Published
- Feb 13, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Crafted ping packet denial-of-service commandfunctional · demonstrated
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