CVE-2021-0097
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 · uneditedPath traversal in the BMC firmware for Intel(R) Server Board M10JNP2SB before version EFI BIOS 7215, BMC 8100.01.08 may allow an unauthenticated user to potentially enable a 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 confidencePath traversal vulnerability in the BMC firmware for Intel Server Board M10JNP2SB allows an unauthenticated attacker with adjacent network access to potentially cause denial of service. The vulnerability exists in versions prior to BMC 8100.01.08 and EFI BIOS 7215.
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< bmc_8100.01.08CVSS 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 the server board modelCheck the server board model via IPMI command 'ipmitool raw' or by inspecting the system via Redfish API at /Systems/System.Embedded.1, or physically locate the board labelAffected if The system is not an Intel Server Board M10JNP2SB (not affected)
-
Check BMC firmware versionRetrieve BMC firmware version using IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U admin -P password mc info' or via Redfish GET to /Managers/BMC.Embedded.1/FirmwareInventoryAffected if BMC firmware version is earlier than 8100.01.08
-
Check EFI BIOS versionRetrieve BIOS version using 'dmidecode -s bios-version' or via Redfish GET to /Systems/System.Embedded.1/Bios.FirmwareInventoryAffected if EFI BIOS version is earlier than 7215
-
Verify BMC network accessibilityConfirm the BMC (IPMI/Redfish) interface is accessible on the network by pinging the BMC IP or checking IPMI LAN status with 'ipmitool -I lanplus -H <BMC_IP> lan print'Affected if BMC is network-accessible and versions in steps 2-3 are below thresholds (attack requires adjacent network access)
The environment is affected if the Intel Server Board M10JNP2SB has BMC firmware prior to 8100.01.08 or EFI BIOS prior to 7215, with the BMC interface network-accessible to an adjacent attacker.
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.
From vendor dataUpdate BMC firmware to version 8100.01.08 or later and EFI BIOS to version 7215 or later. Ensure the update is performed via secure out-of-band management interfaces and validate the integrity of firmware images before applying.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0097 — 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-2021-0097 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