dbcve.org
Liebert Intellislot FirmwareOperating system · Vertiv

CVE-2018-12922

HIGH · 7.5 CVSS v3.1 Published 2018-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Emerson Liebert IntelliSlot Web Card devices allow remote attackers to reconfigure access control via the config/configUser.htm or config/configTelnet.htm URI.

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 confidence

Emerson Liebert IntelliSlot Web Card devices have a broken access control vulnerability where unauthenticated remote attackers can reconfigure access control settings by accessing the config/configUser.htm or config/configTelnet.htm endpoints directly. This allows attackers to modify user accounts, telnet settings, or other access controls without any authentication.

MitigationRestrict network access to the management interface using firewall rules or ACLs to prevent unauthorized external access to the IntelliSlot Web Card configuration pages. If available, apply vendor firmware updates that enforce proper authentication on configuration endpoints.

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
Liebert Intellislot FirmwareOperating system
Affected:all versions

CVSS 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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IntelliSlot Web Card device on your network
    Scan your network for devices responding on HTTP/HTTPS ports (typically 80/443) that return 'IntelliSlot' or 'Liebert' in their web interface title or response headers
    Affected if A Liebert IntelliSlot Web Card device is present and accessible on your network
  2. Confirm web interface is network-accessible
    Attempt to reach the device's web interface from an untrusted network segment (or verify firewall rules allow external access to the device's HTTP port)
    Affected if The IntelliSlot web interface is reachable from a network segment where untrusted users could originate requests
  3. Test unauthenticated access to configUser.htm
    Send an HTTP GET request to http://<device-ip>/config/configUser.htm without providing any authentication credentials and observe the response
    Affected if The endpoint returns a valid configuration page (HTTP 200) instead of requiring authentication (HTTP 401/403) or redirecting to a login page
  4. Test unauthenticated access to configTelnet.htm
    Send an HTTP GET request to http://<device-ip>/config/configTelnet.htm without providing any authentication credentials and observe the response
    Affected if The endpoint returns a valid configuration page (HTTP 200) instead of requiring authentication (HTTP 401/403) or redirecting to a login page
  5. Check for unexpected user account modifications
    If you can access the configUser.htm endpoint, examine the page for user accounts, privilege levels, or authentication settings that you did not configure
    Affected if User accounts exist that were not created by your authorized administrators, or authentication settings appear modified

If the IntelliSlot Web Card web interface is network-accessible and the /config/configUser.htm or /config/configTelnet.htm endpoints are reachable without authentication, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the management interface using firewall rules or ACLs to prevent unauthorized external access to the IntelliSlot Web Card configuration pages. If available, apply vendor firmware updates that enforce proper authentication on configuration endpoints.

Fix this in Liebert Intellislot Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-12922 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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