CVE-2018-3682
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 · uneditedBMC Firmware in Intel server boards, compute modules, and systems potentially allow an attacker with administrative privileges to make unauthorized read\writes to the SMBUS.
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 confidenceThis vulnerability exists in the Baseboard Management Controller (BMC) firmware of Intel server boards, compute modules, and systems. It allows an authenticated attacker with administrative BMC privileges to perform unauthorized read and write operations on the SMBUS (System Management Bus), potentially enabling manipulation of connected hardware components such as sensors, power supplies, or memory modules.
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 dataall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/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 Intel BMC presenceQuery the IPMI interface using command: ipmitool -I open mc info or check for BMC web interface on port 443/80 at the BMC IP addressAffected if System has an Intel Baseboard Management Controller present
-
Determine BMC firmware versionRun: ipmitool -I open mc ver or access BMC web interface and check firmware/revision information in system information or firmware update sectionAffected if BMC firmware version is any Intel BMC firmware (all versions are affected)
-
Confirm SMBUS access is enabledCheck BMC configuration for SMBUS/I2C access settings via IPMI: ipmitool -I raw or via BMC web interface under I2C/SMBus settings or hardware management settingsAffected if SMBUS interface is enabled and accessible from the BMC
-
Review BMC administrative accessList BMC user accounts using: ipmitool -I open user list or check BMC web interface user management panel for administrative accountsAffected if There are BMC administrative accounts configured and accessible (authentication is required for the exploit but attacker needs admin-level BMC credentials)
A user is affected if they have an Intel BMC with any firmware version where SMBUS access is enabled and administrative BMC credentials could be obtained by an 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 dataApply Intel's patched BMC firmware update. Restrict BMC administrative access to authorized personnel only and consider network isolating the BMC from untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3682 — 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-2018-3682 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