dbcve.org
Emc Supportassist EnterpriseApplication · Dell

CVE-2018-1214

HIGH · 7.0 CVSS v3.0 Published 2018-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
Dell EMC SupportAssist Enterprise version 1.1 creates a local Windows user account named "OMEAdapterUser" with a default password as part of the installation process. This unnecessary user account also remains even after an upgrade from v1.1 to v1.2. Access to the management console can be achieved by someone with knowledge of the default password. If SupportAssist Enterprise is installed on a server running OpenManage Essentials (OME), the OmeAdapterUser user account is added as a member of the OmeAdministrators group for the OME. An unauthorized person with knowledge of the default password and access to the OME web console could potentially use this account to gain access to the affected installation of OME with OmeAdministrators privileges. This is fixed in version 1.2.1.

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 confidence

Dell EMC SupportAssist Enterprise v1.1 creates a local Windows user account 'OMEAdapterUser' with a default password during installation. This account persists after upgrading to v1.2 and, when SupportAssist is installed alongside OpenManage Essentials (OME), the account is automatically added to the OmeAdministrators group, granting administrative privileges to anyone with knowledge of the default password.

MitigationUpgrade to version 1.2.1 or later, and manually identify and remove any lingering OMEAdapterUser accounts from the system and OmeAdministrators group if the upgrade did not remove them.

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
Emc Supportassist EnterpriseApplication
Affected:= 1.1

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check for OMEAdapterUser local account existence
    Open Computer Management (compmgmt.msc) and navigate to Local Users and Groups > Users, or run 'net user' command in Command Prompt to list all local user accounts. Look for an account named 'OMEAdapterUser'.
    Affected if The OMEAdapterUser account exists on the system (indicates v1.1 was installed and the account was created, or upgrade did not remove it).
  2. Verify OMEAdapterUser membership in OmeAdministrators group
    Open Computer Management > Local Users and Groups > Groups > OmeAdministrators, or run 'net localgroup OmeAdministrators' command. Check if OMEAdapterUser is listed as a member.
    Affected if OMEAdapterUser is a member of the OmeAdministrators group (grants administrative privileges to anyone with the default password).
  3. Confirm OpenManage Essentials co-existence
    Check installed programs list for 'OpenManage Essentials' or 'OME' via Control Panel > Programs and Features, or check the system for OME installation directories or services.
    Affected if OpenManage Essentials is installed alongside SupportAssist Enterprise (the condition required for automatic group membership addition).

User is affected if the OMEAdapterUser account exists AND is a member of OmeAdministrators group while OpenManage Essentials is present on the system.

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

Upgrade to version 1.2.1 or later, and manually identify and remove any lingering OMEAdapterUser accounts from the system and OmeAdministrators group if the upgrade did not remove them.

Fix this in Emc Supportassist Enterprise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1214 — 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-1214 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