CVE-2019-3721
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 Open Manage System Administrator (OMSA) versions prior to 9.3.0 contain an Improper Range Header Processing Vulnerability. A remote unauthenticated attacker may send crafted requests with overlapping ranges to cause the application to compress each of the requested bytes, resulting in a crash due to excessive memory consumption and preventing users from accessing the 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 confidenceDell EMC Open Manage System Administrator versions prior to 9.3.0 have improper HTTP Range header processing. A remote unauthenticated attacker can send crafted requests with overlapping byte ranges, causing the application to compress each requested byte individually, leading to excessive memory consumption and crash.
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< 9.3.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify Dell EMC OMSA installationOn Windows: Check installed programs or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for 'OpenManage' or 'OMSA'. On Linux: run 'rpm -qa | grep -i openmanage' or 'dpkg -l | grep -i openmanage'Affected if Dell EMC OpenManage Server Administrator is found installed on the system
-
Identify installed OMSA versionOn Windows: Check Add/Remove Programs or the registry DisplayVersion value under the OMSA uninstall key. On Linux: run 'rpm -q dsm-om' or check /opt/dell/srvadmin/etc/omreporter.cfg for version infoAffected if The version number returned is lower than 9.3.0 (for example, 9.2.0, 9.1.0, etc.)
-
Confirm web management interface is enabledOn Windows: Check if 'DSM SaaS' or 'Dell OpenManage Server Administrator' service is running via Services.msc. On Linux: check if 'dsmadmd' or 'dce_svcmain' process is running, or check /etc/init.d for srvadmin-servicesAffected if The OMSA web server service (DSM Service or dsmadmd) is running and accessible on HTTP/HTTPS ports (typically 1311)
If Dell EMC OpenManage Server Administrator is installed with a version prior to 9.3.0 and the web management service is running, the environment is affected by this improper HTTP Range header vulnerability.
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 data9.3.0
Upgrade to Dell EMC OMSA version 9.3.0 or later, which contains the fix for improper Range header processing.
- Consultation2.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3721 — 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-2019-3721 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