CVE-2018-12173
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 · uneditedInsufficient access protection in firmware in Intel Server Board, Intel Server System and Intel Compute Module before firmware version 00.01.0014 may allow an unauthenticated attacker to potentially execute arbitrary code resulting in information disclosure, escalation of privilege and/or denial of service via local 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 confidenceInsufficient access protection in the firmware of Intel Server Board, Intel Server System, and Intel Compute Module allows an unauthenticated attacker with local access to potentially execute arbitrary code, achieve privilege escalation, cause denial of service, or disclose information. The vulnerability exists in versions prior to 00.01.0014.
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< 00.01.0014< 00.01.0014< 00.01.0014< 00.01.0014< 00.01.0014< 00.01.0014< 00.01.0014< 00.01.0014CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/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 the exact Intel server board or compute module modelPhysically label or use BMC/IPMI to identify whether the system is one of: S2600bp, S2600wf, S2600st, S2600bpr, S2600wfr, S2600str, Hns2600bp, or Hns2600bprAffected if The model matches one of the listed affected products
-
Retrieve the current firmware version via BMC/IPMIUse IPMItool command 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw' or access the BMC web interface to view the firmware version. Alternatively, check in BIOS/UEFI setup under 'System Information' or 'Firmware Version'Affected if The displayed firmware version is lower than 00.01.0014 or shows a version without the 00.01.0014 build string
-
Verify the BMC user access controlsCheck BMC user list and privilege levels via IPMItool 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> user list' or through BMC web interface under User ManagementAffected if Unauthenticated or low-privilege local access to the BMC is possible or users with limited privileges can access sensitive BMC functions
-
Confirm local console access exposureInspect physical access to the server and check if IPMI Serial-over-LAN (SOL) or KVM-over-IP is enabled with weak authenticationAffected if Local console or IPMI interfaces are accessible to unauthorized personnel
A user is affected if they have an Intel Server Board S2600bp/wf/st/bpr/wfr/str or Compute Module Hns2600bp/bpr running firmware version prior to 00.01.0014 and the system has local physical or console access exposure.
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 data00.01.0014
Update Intel server firmware to version 00.01.0014 or later. Since this is a local access vulnerability, ensure physical security of server infrastructure and restrict console access.
- Consultation12.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12173 — 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-12173 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