Emc Omimssc For SccmApplication · Dell

CVE-2020-5373

HIGH · 7.5 CVSS v3.1 Published 2020-07-14
Fix available
A fix is available. Upgrade to 7.2.1 or later.
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
Dell EMC OpenManage Integration for Microsoft System Center (OMIMSSC) for SCCM and SCVMM versions prior to 7.2.1 contain an improper authentication vulnerability. A remote unauthenticated attacker may potentially exploit this vulnerability to retrieve the system inventory data of the managed device.

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 OpenManage Integration for Microsoft System Center (OMIMSSC) versions prior to 7.2.1 contain an improper authentication vulnerability. A remote unauthenticated attacker can exploit missing or insufficient authentication checks on certain endpoints to retrieve sensitive system inventory data from managed devices without any credentials.

MitigationUpgrade to OMIMSSC version 7.2.1 or later to address the improper authentication vulnerability. Until patched, network access to OMIMSSC should be restricted to trusted management networks only.

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 Omimssc For SccmApplication
Affected:< 7.2.1
Emc Omimssc For ScvmmApplication
Affected:< 7.2.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify OMIMSSC installation and version
    Check installed programs list in Windows Control Panel > Programs and Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'OpenManage Integration for Microsoft System Center' or 'OMIMSSC'. Note the installed version.
    Affected if Installed version is lower than 7.2.1
  2. Confirm product type (SCCM or SCVMM)
    Check whether the installation is Dell EMC OMIMSSC for SCCM (Systems Center Configuration Manager) or for SCVMM (System Center Virtual Machine Manager). This determines which integration component is deployed. Look at the program name in Add/Remove Programs or check installation logs.
    Affected if Either product variant is installed with version below 7.2.1
  3. Identify exposed management endpoints
    Locate the OMIMSSC web service configuration files (typically in the installation directory, often under C:\Program Files\Dell\EMOMIMSSC or similar). Check for exposed HTTP/HTTPS endpoints in the configuration files or IIS settings if hosted in IIS.
    Affected if Management or API endpoints are accessible over network without authentication required
  4. Test endpoint accessibility without credentials
    From a remote system, attempt to access common OMIMSSC endpoints such as /api/inventory or /api/devices without providing any authentication credentials. Use a browser or curl command to send unauthenticated requests.
    Affected if Requests to sensitive endpoints return successful responses containing system inventory or device data without authentication prompts

A system is affected if OMIMSSC version is below 7.2.1 AND the vulnerable authentication endpoints are exposed and accessible without credentials.

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
Upgrade available Upgrade to 7.2.1 or later
Fixed in 7.2.1
Interim mitigation

Upgrade to OMIMSSC version 7.2.1 or later to address the improper authentication vulnerability. Until patched, network access to OMIMSSC should be restricted to trusted management networks only.

Fix this in Emc Omimssc For Sccm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5373 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5373 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