CVE-2019-11182
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 · uneditedMemory corruption in Intel(R) Baseboard Management Controller 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 confidenceMemory corruption vulnerability in Intel Baseboard Management Controller (BMC) firmware. BMCs are out-of-band management processors in servers that provide IPMI-based remote management. An unauthenticated attacker with network access to the BMC interface (typically port 623 UDP) can exploit memory corruption to cause denial of service, potentially crashing the BMC or rendering server management functions unavailable.
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.18CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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.
-
Confirm Intel BMC is presentCheck if the server has an Intel Baseboard Management Controller by querying IPMI: run `ipmitool mc info` or check the BMC web interface for Intel BMC firmware.Affected if The system does not have an Intel BMC, this CVE does not apply.
-
Check BMC firmware versionRetrieve the BMC firmware version using IPMI command: `ipmitool -I lanplus -H <BMC_IP> -U admin -P password mc info` or access the BMC web interface and locate the firmware version under the firmware or system information section.Affected if The installed firmware version is less than 2.18.
-
Verify BMC network accessibilityConfirm that UDP port 623 (the IPMI remote management port) is open and reachable on the BMC interface by scanning: `nmap -sU -p 623 <BMC_IP>` or checking firewall rules.Affected if The BMC is accessible over the network on port 623, exposing it to potential remote attackers.
-
Check IPMI protocol settingsReview IPMI configuration via IPMI: `ipmitool -I lanplus -H <BMC_IP> -U admin -P password raw` commands or via the BMC web interface to see if remote IPMI/UDP port 623 is enabled.Affected if Remote IPMI access is enabled and allows unauthenticated or network-accessible connections.
The environment is affected if an Intel BMC is present with firmware version below 2.18 and the BMC management port 623 is network-accessible.
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.18
Apply Intel BMC firmware updates when available. As immediate mitigation, network-segment BMC interfaces away from untrusted networks, restrict access to authorized management IPs only, and consider disabling remote IPMI access if not required.
- Consultation4.0 h
- Implementation8.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11182 — 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-2019-11182 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