dbcve.org
Emc Openmanage Enterprise ModularApplication · Dell

CVE-2020-5322

CRITICAL · 9.1 CVSS v3.1 Published 2021-07-19
Fix available
A fix is available. Upgrade to 1.10.00 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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 Enterprise-Modular (OME-M) versions prior to 1.10.00 contain a command injection vulnerability. A remote authenticated malicious user with high privileges could potentially exploit the vulnerability to execute arbitrary shell commands on the affected system.

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 Enterprise-Modular versions prior to 1.10.00 contain a command injection vulnerability in the web interface. A remote authenticated attacker with high privileges can inject and execute arbitrary shell commands on the underlying operating system by crafting malicious input in vulnerable parameters.

MitigationUpgrade to Dell EMC OpenManage Enterprise-Modular version 1.10.00 or later to obtain the patched codebase. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious command activity.

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 Openmanage Enterprise ModularApplication
Affected:< 1.10.00

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 installed OpenManage Enterprise-Modular version
    Access the OMEM admin console or use the REST API endpoint /api/Platform.EmbeddedSoftwareIdentity to retrieve the current installed version. Alternatively, check the software inventory via the web UI under 'Software > Firmware' or use the 'omreport' CLI tool if available.
    Affected if The reported version is below 1.10.00 (e.g., 1.0.x, 1.1.x, 1.2.x, 1.3.x, 1.4.x, 1.5.x, 1.6.x, 1.7.x, 1.8.x, or 1.9.x).
  2. Verify web interface is enabled and accessible
    Confirm that the OpenManage Enterprise-Modular web console is enabled by checking the server's network configuration. Attempt to access the HTTPS management portal from an authorized network.
    Affected if The web interface is exposed and accessible from the network where the check is performed.
  3. Review audit logs for high-privilege user activity
    Examine the OMEM audit logs located in the system logs directory or accessible via the web UI under 'Logs > Audit'. Look for entries from users with Administrator or equivalent high-privilege roles, especially those containing unusual command patterns or shell metacharacters.
    Affected if Audit logs show commands or requests containing shell metacharacters (such as ; | & $ ` or backticks) submitted by high-privilege users, or requests to unexpected endpoints.

You are affected if your installed OpenManage Enterprise-Modular version is prior to 1.10.00 AND the web interface is accessible, regardless of whether malicious activity has been observed in logs.

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.

dbcve · scoped
Upgrade available Upgrade to 1.10.00 or later
Fixed in 1.10.00
Interim mitigation

Upgrade to Dell EMC OpenManage Enterprise-Modular version 1.10.00 or later to obtain the patched codebase. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious command activity.

Recommended fix High confidence

1.10.00 (Dell EMC OpenManage Enterprise-Modular)

  1. Verify current OME-M version by navigating to Settings > About in the OME-M web interface
  2. Download the OME-M version 1.10.00 or later from Dell EMC support (support.dell.com) using your account with valid entitlements
  3. Review the OME-M upgrade guide and release notes for version 1.10.00 for any pre-upgrade requirements
  4. Create a full backup of the OME-M configuration and data
  5. Schedule a maintenance window as the upgrade may require system downtime
  6. Upload the upgrade bundle through the OME-M web interface under Settings > Update Firmware, or use the OME-M CLI for the upgrade procedure
  7. Monitor the upgrade progress and verify the system becomes accessible after completion
  8. Confirm the installed version shows 1.10.00 or later in the About section

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Emc Openmanage Enterprise Modular Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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