CVE-2019-3722
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 Server Administrator (OMSA) versions prior to 9.1.0.3 and prior to 9.2.0.4 contain an XML external entity (XXE) injection vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability to read arbitrary server system files by supplying specially crafted document type definitions (DTDs) in an XML request.
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 OpenManage Server Administrator (OMSA) versions prior to 9.1.0.3 and 9.2.0.4 contain an XML External Entity (XXE) injection vulnerability. A remote unauthenticated attacker can send specially crafted XML requests containing malicious Document Type Definitions (DTDs) to read arbitrary files from the server filesystem.
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.1= 9.1.0.1= 9.1.0.2= 9.2= 9.2.0.1= 9.2.0.2CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Check if OMSA is installedLook for Dell EMC OpenManage Server Administrator installation. On Windows, check Program Files for 'Dell' or 'OpenManage' folder. On Linux, run: rpm -qa | grep -i openmanage or dpkg -l | grep -i openmanageAffected if OMSA is not installed on the system
-
Determine the installed OMSA versionOn Windows, check Add/Remove Programs or the installation directory for version info. On Linux, run: /opt/dell/srvadmin/bin/omreport about 2>/dev/null or rpm -q srvadmin-allAffected if The version displayed matches 9.1, 9.1.0.1, 9.1.0.2, 9.2, 9.2.0.1, or 9.2.0.2
-
Verify OMSA services are runningOn Windows, check if 'DSM SA Data Manager' or 'srvadmin' services are running via Services.msc. On Linux, run: service srvadmin-status or check process: ps aux | grep -i srvadminAffected if OMSA services are actively running
-
Check if OMSA web interface is accessibleTest if port 1311 (default OMSA HTTP port) is listening and reachable: telnet <server-ip> 1311 or curl -I http://localhost:1311Affected if The web interface responds to requests, indicating it is exposed
-
Confirm version is in affected rangeCompare your installed version against the affected list: 9.1, 9.1.0.1, 9.1.0.2, 9.2, 9.2.0.1, 9.2.0.2. Versions 9.1.0.3 and 9.2.0.4 and later are NOT affected.Affected if The installed version is one of the affected versions listed and the web interface is reachable
You are affected if Dell EMC OpenManage Server Administrator is installed, running, and the installed version is 9.1.x (before 9.1.0.3) or 9.2.x (before 9.2.0.4), with the web interface accessible on the network.
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 dataUpgrade OMSA to version 9.1.0.3 or 9.2.0.4 or later. If upgrading is not immediately possible, consider restricting network access to the OMSA web interface via firewall or ACLs.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3722 — 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-3722 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