CVE-2018-12172
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 · uneditedImproper password hashing in firmware in Intel Server Board (S7200AP,S7200APR) and Intel Compute Module (HNS7200AP, HNS7200AP) may allow a privileged user to potentially disclose firmware passwords 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 · moderate confidenceImproper password hashing implementation in firmware for Intel Server Boards (S7200AP, S7200APR) and Intel Compute Modules (HNS7200AP) allows a user with privileged local access to potentially disclose firmware passwords. The vulnerability stems from weak or absent cryptographic protection of stored passwords in the firmware.
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= r01.03.0018= r01.03.0018= r01.03.0018= r01.03.0018CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 server board or compute module modelPhysically inspect the server hardware labeling or use IPMI/BMC web interface or CLI (ipmitool) to query the system product information. Look for model numbers S7200AP, S7200APR, HNS7200AP, or HNS7200APR.Affected if The installed hardware is one of these four models: S7200AP, S7200APR, HNS7200AP, or HNS7200APR.
-
Check the installed firmware versionAccess the BMC/IPMI interface via web UI or use command line tool (ipmitool) with 'mc info' or 'fwuploader' utility from Intel to query the current firmware version. Compare against the affected version r01.03.0018.Affected if The firmware version is r01.03.0018 or earlier on an affected model.
-
Verify if local firmware passwords are configuredAccess the BIOS/UEFI setup or BMC configuration interface and check if local administrator or user passwords have been set in the firmware. This includes BIOS passwords, IPMI user passwords, or other firmware-level authentication.Affected if Local privileged user accounts with firmware passwords exist on the system.
A system is affected if it is an Intel S7200AP, S7200APR, HNS7200AP, or HNS7200APR model running firmware version r01.03.0018 or earlier and has local firmware passwords configured for privileged access.
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 dataUpdate Intel firmware to version(s) that implement proper password hashing algorithms. Restrict local privileged access to only trusted administrators until patches are applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12172 — 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-12172 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