dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2024-36274

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Out-of-bounds write in the Intel(R) 800 Series Ethernet Driver for Intel(R) Ethernet Adapter Complete Driver Pack before versions 29.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 confidence

An out-of-bounds write vulnerability exists in Intel(R) 800 Series Ethernet Driver versions prior to 29.1. An unauthenticated attacker with adjacent network access can trigger this flaw to potentially cause a denial of service condition.

MitigationUpdate to Intel Ethernet Adapter Complete Driver Pack version 29.1 or later to address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intel 800 Series Ethernet adapter present
    On Windows: open Device Manager, expand Network adapters, look for Intel(R) Ethernet 800 Series entries. On Linux: run 'lspci | grep -i intel.*ethernet' or 'ip link show' to list network interfaces
    Affected if No Intel 800 Series Ethernet adapter is listed in system hardware
  2. Retrieve installed driver version on Windows
    Open Device Manager, right-click the Intel 800 Series Ethernet adapter, select Properties, go to Driver tab, note the Driver Version field. Alternatively, run 'driverquery /v | findstr -i intel' in Command Prompt
    Affected if Driver version number is lower than 29.1 (e.g., 28.x, 27.x, etc.)
  3. Retrieve installed driver version on Linux
    Run 'ethtool -i <interface>' where <interface> is the Intel 800 Series interface (e.g., eth0, ens33f0). The driver version appears in the 'driver:' field. Also check 'modinfo ice' for driver module version
    Affected if Driver version displayed is lower than 29.1 or the module version is below 29.1
  4. Check driver date as alternative version indicator
    In Device Manager on Windows, the Driver Date field on the Driver tab may indicate version. On Linux, 'modinfo ice | grep version' shows module version. Compare the date to the 29.1 release timeframe (2024)
    Affected if Driver date is prior to 2024 or driver version cannot be confirmed as 29.1 or later

System is affected if an Intel 800 Series Ethernet adapter is present with a driver version prior to 29.1, as versions below this threshold contain the out-of-bounds write flaw exploitable via adjacent network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to Intel Ethernet Adapter Complete Driver Pack version 29.1 or later to address this vulnerability.

Recommended fix Moderate confidence

Intel Ethernet Adapter Complete Driver Pack version 29.1 or later

  1. Identify the currently installed Intel(R) 800 Series Ethernet Driver version on the affected system
  2. Navigate to the Intel Support website or use Intel Driver & Support Assistant to check for driver updates
  3. Download the Intel Ethernet Adapter Complete Driver Pack version 29.1 or later
  4. Backup existing network configurations as a precautionary measure
  5. Install the updated driver package following the provided installation instructions
  6. Restart the system to ensure the new driver is properly loaded
  7. Verify the driver version post-installation to confirm the update was successful
Caveat Driver updates typically do not introduce breaking changes but may require system restart; ensure network connectivity alternatives are available during update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36274 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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