CVE-2020-24474
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 · uneditedBuffer overflow in the BMC firmware for some Intel(R) Server Boards, Server Systems and Compute Modules before version 2.48.ce3e3bd2 may allow an authenticated user to potentially enable escalation of privilege 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 confidenceA buffer overflow vulnerability exists in the BMC (Baseboard Management Controller) firmware for certain Intel server boards, systems, and compute modules. The flaw allows an authenticated user with adjacent network access to potentially escalate privileges. The vulnerability is patched in version 2.48.ce3e3bd2 and later.
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< 2.48.ce3e3bd2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Locate the BMC interface addressIdentify the IP address or hostname of the Baseboard Management Controller. This is typically found in server BIOS/UEFI settings under BMC network configuration, or by checking your network for devices responding on IPMI ports (623/UDP).Affected if The BMC IP address is reachable on the network.
-
Obtain BMC firmware version via IPMIRun command: ipmitool -I lanplus -H <bmc-ip> -U <username> -P <password> mc info. This returns BMC version information including the firmware build string.Affected if The displayed firmware version string is earlier than 2.48.ce3e3bd2.
-
Obtain BMC firmware version via web interfaceAccess the BMC web UI at https://<bmc-ip> and navigate to Settings > Firmware Update or System Information > BMC Information. Locate the firmware version or build string displayed.Affected if The displayed firmware version string is earlier than 2.48.ce3e3bd2.
-
Obtain BMC firmware version via Redfish APISend a GET request to https://<bmc-ip>/redfish/v1/Managers/1 and examine the FirmwareVersion or BuildNumber field in the JSON response.Affected if The returned firmware version is earlier than 2.48.ce3e3bd2.
-
Confirm authentication is requiredVerify that the vulnerability requires an authenticated user. Ensure you have valid BMC credentials (or confirm your security team does).Affected if Valid BMC user credentials exist in the environment, making the privilege escalation path applicable.
You are affected if your Intel BMC firmware version is below 2.48.ce3e3bd2 and the BMC is network-accessible with valid user accounts configured.
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 data2.48.ce3e3bd2
Apply the Intel firmware update version 2.48.ce3e3bd2 or later to all affected Intel Server Boards, Server Systems, and Compute Modules. Restrict adjacent network access to BMC management interfaces and limit BMC user accounts to only those necessary.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24474 — 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-2020-24474 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