CVE-2018-16096
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 · uneditedIn System Management Module (SMM) versions prior to 1.06, the SMM web interface for changing Enclosure VPD fails to sufficiently sanitize all input for HTML tags, possibly opening a path for cross-site scripting.
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 confidenceThis is a stored (persistent) cross-site scripting (XSS) vulnerability in the System Management Module (SMM) web interface. The Enclosure VPD (Vital Product Data) input fields fail to properly sanitize HTML tag input, allowing malicious JavaScript to be injected and stored. When other users access the web interface to view the Enclosure VPD, the embedded scripts execute in their browsers.
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.06CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify SMM web interface is accessibleAttempt to access the System Management Module web interface via HTTP/HTTPS on the management IP (typically on ports 80, 443, or a custom management port). Confirm the login page or web UI loads.Affected if The SMM web interface is reachable on the network and accepts authentication.
-
Locate the firmware version in the SMM web interfaceLog into the SMM web interface and navigate to the System Information, About, or Firmware Version section. The firmware version is typically displayed on the main dashboard or under a Settings/Configuration menu. Alternatively, access the SMM via IPMI or command line (e.g., ipmitool -I lanplus -H <IP> -U <user> raw command) to retrieve firmware version information.Affected if The firmware version displayed is below 1.06.
-
Compare installed version to affected rangeNote the exact firmware version string (e.g., 1.00, 1.02, 1.05). Compare this against the affected range of versions less than 1.06.Affected if The installed SMM firmware version is 1.05 or lower.
-
Verify Enclosure VPD feature is accessibleWithin the SMM web interface, navigate to the Enclosure VPD (Vital Product Data) section. This is typically found under Hardware Monitoring, System Health, or Inventory menus. Confirm the page loads and displays input fields for Enclosure VPD data.Affected if The Enclosure VPD input fields are available and editable in the web interface.
If the SMM firmware version is below 1.06 and the Enclosure VPD web interface feature is accessible, the system is vulnerable to stored XSS via the Enclosure VPD input fields.
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 data1.06
Upgrade to SMM version 1.06 or later which contains the patch for proper input sanitization. As an interim measure, implement output encoding and input validation on the Enclosure VPD fields to neutralize HTML/script tags.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16096 — 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-16096 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