Ethernet Controller I225 It FirmwareOperating system · Intel

CVE-2021-33141

HIGH · 8.6 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to 1.87 / 29.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
Improper input validation in some Intel(R) Ethernet Adapters and Intel(R) Ethernet Controller I225 Manageability firmware may allow an unauthenticated user to potentially enable denial of service via network 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 · moderate confidence

Improper input validation in Intel Ethernet Adapters and Intel Ethernet Controller I225 Manageability firmware allows unauthenticated remote attackers to cause denial of service via specially crafted network packets. The vulnerability stems from insufficient validation of input data processed by the manageability firmware component.

MitigationApply Intel firmware updates for affected Ethernet adapters and I225 controllers. If updates are unavailable, consider network segmentation to limit exposure and disabling manageability features if not required.

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
Ethernet Controller I225 It FirmwareOperating system
Affected:< 1.87
Ethernet Controller I225 Lm FirmwareOperating system
Affected:< 1.87
Ethernet Controller I225 V FirmwareOperating system
Affected:< 1.87
Ethernet Adapter Complete DriverApplication
Affected:< 29.0.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 I225 hardware in the system
    Check system hardware inventory or use 'lspci' command to list network controllers and look for 'Ethernet Controller I225' entries
    Affected if No Intel I225 adapter is found, this CVE does not apply to the system
  2. Check I225 firmware version
    Access the manageability firmware interface (e.g., Intel AMT, Intel ME or vendor-specific management tool) to read the firmware version. For It, Lm, and V variants, verify the version number
    Affected if Firmware version is below 1.87 for any I225 variant (It, Lm, or V)
  3. Verify manageability firmware is enabled
    Check the manageability settings in BIOS/UEFI or through the Intel management engine interface. Look for settings related to 'Manageability', 'AMT', or 'ME' that control the manageability firmware component
    Affected if Manageability features are enabled and the I225 firmware version is below 1.87 - this is the vulnerable configuration
  4. Check Intel Ethernet Adapter driver version (if applicable)
    Use 'ethtool -i <interface>' or check driver details through the operating system's network adapter properties to identify the driver version
    Affected if Using Intel Ethernet Adapter Complete Driver version below 29.0.1 with an affected I225 controller

The system is affected if it has an Intel Ethernet Controller I225 with firmware version below 1.87 AND the manageability firmware component is enabled/active.

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
Upgrade available Upgrade to 1.87 / 29.0.1 or later
Fixed in 1.8729.0.1
Interim mitigation

Apply Intel firmware updates for affected Ethernet adapters and I225 controllers. If updates are unavailable, consider network segmentation to limit exposure and disabling manageability features if not required.

Recommended fix High confidence

Firmware: 1.87 or later | Driver: 29.0.1 or later

  1. Identify the specific Intel Ethernet Controller I225 variant (IT, LM, or V) in your environment
  2. Download the Intel Ethernet Controller I225 firmware version 1.87 or later from Intel's support site
  3. Download the Intel Ethernet Adapter Complete Driver version 29.0.1 or later from Intel's support site
  4. Apply the firmware update to the affected Ethernet Controller I225 devices following Intel's firmware update instructions
  5. Install the updated Ethernet Adapter Complete Driver (version 29.0.1 or later) on affected systems
  6. Verify the firmware and driver versions have been successfully updated
Caveat Firmware updates may require a reboot or network downtime; ensure proper change management procedures are followed

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

Fix this in Ethernet Controller I225 It Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33141 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33141 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