CVE-2021-0113
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 write 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 confidenceThis CVE describes an out-of-bounds write vulnerability in the Baseboard Management Controller (BMC) firmware of the Intel Server Board M10JNP2SB. The flaw allows an unauthenticated attacker with adjacent network access to potentially cause a denial of service via memory corruption. The vulnerability exists in versions prior to EFI BIOS 7215 and BMC 8100.01.08.
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 modelRun 'dmidecode -s system-product-name' or check system inventory to confirm the hardware is an Intel Server Board M10JNP2SBAffected if The system is not an Intel Server Board M10JNP2SB, as this vulnerability only affects that specific model
-
Check the EFI BIOS versionRun 'dmidecode -s bios-version' or use IPMI to query the BIOS version, then compare it against version 7215Affected if The EFI BIOS version is below 7215 (for example, 7200 or earlier)
-
Check the BMC firmware versionUse IPMI to query the BMC version, such as 'ipmitool -I lanplus -H <BMC_IP> -U <user> bmc info' or access the BMC web interface to view firmware version information, then compare it against 8100.01.08Affected if The BMC firmware version is below 8100.01.08 (for example, 8100.01.07 or earlier)
-
Verify BMC network accessibilityCheck if the BMC IPMI interface is reachable from the network using ping or a port scan to confirm the BMC is network-accessibleAffected if The BMC is directly reachable on the network, as the vulnerability requires adjacent network access to exploit
The system is affected if it is an Intel Server Board M10JNP2SB with EFI BIOS version below 7215 AND BMC version below 8100.01.08, with the BMC accessible on the network.
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 dataApply the vendor-provided firmware update to EFI BIOS version 7215 and BMC version 8100.01.08 or later. Schedule the update during a maintenance window due to the critical nature of BMC firmware updates and ensure proper rollback procedures are in place.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0113 — 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-0113 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