CVE-2020-5323
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 · uneditedDell EMC OpenManage Enterprise (OME) versions prior to 3.2 and OpenManage Enterprise-Modular (OME-M) versions prior to 1.10.00 contain an injection vulnerability. A remote authenticated malicious user with low privileges could potentially exploit this vulnerability to gain access to sensitive information or cause denial-of-service.
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 confidenceDell EMC OpenManage Enterprise (OME) versions before 3.2 and OpenManage Enterprise-Modular (OME-M) versions before 1.10.00 contain an injection vulnerability. A remote authenticated attacker with low-privilege credentials can exploit this vulnerability to potentially gain unauthorized access to sensitive information or cause a denial-of-service condition.
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< 3.2< 1.10.00CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed OpenManage productLog into the OpenManage Enterprise or OpenManage Enterprise-Modular web interface and locate the product name displayed in the console header or system information pageAffected if The product is either Dell EMC OpenManage Enterprise or Dell EMC OpenManage Enterprise-Modular
-
Find the installed version of OpenManage EnterpriseIn the OME web interface, navigate to Settings > About or System > Inventory to view the software version numberAffected if The version displayed is lower than 3.2 (for example, 3.1, 3.0, or earlier)
-
Find the installed version of OpenManage Enterprise-ModularIn the OME-M web interface, navigate to Settings > About or the Modular System overview page to view the software version numberAffected if The version displayed is lower than 1.10.00 (for example, 1.00.00, 1.01.00, or earlier)
-
Verify remote access is enabledConfirm that the OpenManage web interface is accessible over the network and that user authentication is configuredAffected if The product is reachable remotely and user accounts exist, allowing an authenticated attacker with low-privilege credentials to attempt exploitation
A system is affected if it is running Dell EMC OpenManage Enterprise version lower than 3.2 or OpenManage Enterprise-Modular version lower than 1.10.00, and the web interface is accessible for remote authenticated access.
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.10.003.2
Upgrade Dell EMC OpenManage Enterprise to version 3.2 or later, and OpenManage Enterprise-Modular to version 1.10.00 or later to remediate this vulnerability.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5323 — 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-2020-5323 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