CVE-2013-1634 json
A denial of service vulnerability exists in some motherboard implementations of Intel e1000e/82574L network controller devices through 2013…
published 6y ago modified 4mo ago also EUVD-2013-1665
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
A denial of service vulnerability exists in some motherboard implementations of Intel e1000e/82574L network controller devices through 2013-02-06 where the device can be brought into a non-processing state when parsing 32 hex, 33 hex, or 34 hex byte values at the 0x47f offset. NOTE: A followup statement from Intel suggests that the root cause of this issue was an incorrectly configured EEPROM image.
Is CVE-2013-1634 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.49% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-665 Improper Initialization
References
-
web.archive.org
/web/20131205055429/https://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-etherne
vendor-advisory
-
securitytracker.com
/id/1028089
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2013/02/12/4
mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2013/02/12/3
mailing-list, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/85069
vdb-entry, third-party-advisory
-
blog.krisk.org
/2013/02/packets-of-death.html
technical-description, third-party-advisory
Sources
- CVE List CVE-2013-1634
- NVD CVE-2013-1634
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.