CVE-2023-28376
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOut-of-bounds read in the firmware for some Intel(R) E810 Ethernet Controllers and Adapters before version 1.7.1 may allow an unauthenticated user to potentially enable denial of service via adjacent access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn out-of-bounds read vulnerability exists in the firmware of Intel E810 Ethernet Controllers and Adapters before version 1.7.1. An unauthenticated attacker with adjacent network access could exploit this to read unintended memory contents, potentially causing a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.7.1< 1.7.1< 1.7.1< 1.7.1< 1.7.1< 1.7.1< 1.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Intel E810 adapter presenceCheck system hardware inventory or use 'lspci | grep -i ether' on Linux or 'Get-NetAdapter' in PowerShell on Windows to list network adaptersAffected if No Intel E810 adapter is found in the system
-
Retrieve firmware version from the adapterUse 'ethtool -i <interface>' on Linux or Intel firmware utility on Windows to query the firmware version of the E810 adapterAffected if Firmware version cannot be retrieved or is below 1.7.1
-
Compare firmware version to vulnerability thresholdCompare the installed firmware version number to the affected range: any version less than 1.7.1 is vulnerableAffected if Installed firmware version is < 1.7.1 (for example, 1.5.3, 1.6.0, etc.)
-
Verify attack surface exposureConfirm the adapter is connected to a network where an adjacent attacker could send crafted packets to the E810 interfaceAffected if Adapter is on an accessible network segment and firmware version is < 1.7.1
The system is affected if an Intel E810 Ethernet adapter with firmware version below 1.7.1 is present and has adjacent network exposure.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.7.1
Update Intel E810 firmware to version 1.7.1 or later to remediate this vulnerability.
Firmware version 1.7.1 for Intel E810 Ethernet Adapters
- Identify the specific Intel E810 adapter model (e.g., E810-CQDA2, E810-2CQDA2, etc.) in your system
- Download the firmware version 1.7.1 or later from Intel's support website (www.intel.com) for your specific adapter model
- Use Intel's Ethernet firmware update tool or the adapter's firmware update interface to apply the new firmware
- Reboot the system or reset the adapter after firmware update to ensure the new firmware is loaded
- Verify the firmware version has been updated to 1.7.1 or later using the adapter management tools
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28376 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data