CVE-2019-16649
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 · uneditedOn Supermicro H11, H12, M11, X9, X10, and X11 products, a combination of encryption and authentication problems in the virtual media service allows capture of BMC credentials and data transferred over virtual media devices. Attackers can use captured credentials to connect virtual USB devices to the server managed by the BMC.
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 confidenceSupermicro BMCs across H11, H12, M11, X9, X10, and X11 product lines contain combined encryption and authentication flaws in the virtual media service. Attackers can intercept BMC credentials and data in transit, then leverage captured credentials to attach malicious virtual USB devices to server operating systems.
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= 1.71.5= 1.71.5= 1.71.5= 1.71.5= 1.71.5= 1.71.5= 1.71.5= 1.71.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify Supermicro BMC modelAccess the BMC web interface or use IPMI command 'ipmitool -I lanplus -U ADMIN -P ADMIN mc info' to retrieve the BMC product name and model number. Look for H11, H12, M11, X9, X10, or X11 product lines.Affected if The BMC model is one of the affected product lines (H11, H12, M11, X9, X10, X11).
-
Check BMC firmware versionIn the BMC web interface, navigate to the firmware version information page, or run 'ipmitool -I lanplus -U ADMIN -P ADMIN mc info' to retrieve the firmware revision. Compare the installed version against the affected versions listed.Affected if Firmware version equals exactly 1.71.5 on any of the listed X11 models (X11dai N, X11dac, X11dph Tq, X11dph I, X11dph T, X11dps Re, X11dsf E, X11dsn Ts).
-
Verify virtual media service statusCheck if the virtual media feature is enabled in the BMC configuration under IPMI or Web interface settings. Use 'ipmitool -I lanplus -U ADMIN -P ADMIN raw commands' or web UI to query virtual media status.Affected if Virtual media service is enabled on the BMC.
-
Assess network accessibility of BMCDetermine if the BMC management interface (IP address) is reachable from untrusted networks. Check firewall rules, VLAN configuration, and network segmentation around the BMC IP address.Affected if The BMC or virtual media interface is accessible from untrusted or management-untrusted networks.
A user is affected if they run a Supermicro BMC from the H11/H12/M11/X9/X10/X11 lines with firmware version 1.71.5 on an affected X11 model, with virtual media enabled and accessible over 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 Supermicro BMC firmware updates addressing this vulnerability; if no update available, restrict network access to the BMC and virtual media interfaces to trusted management networks only.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16649 — 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-16649 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