CVE-2019-3723
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 a web parameter tampering vulnerability. A remote unauthenticated attacker could potentially manipulate parameters of web requests to OMSA to create arbitrary files with empty content or delete the contents of any existing file, due to improper input parameter validation
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 contains a web parameter tampering vulnerability where improper input validation allows a remote unauthenticated attacker to manipulate web request parameters. Attackers can create arbitrary empty files anywhere on the system or delete contents of existing files by tampering with web parameters.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify OMSA installation existsCheck for Dell EMC OpenManage Server Administrator installation. On Windows, look in Program Files for 'Dell\OpenManage' or check registry key HKLM\SOFTWARE\Dell\OpenManage. On Linux, run 'rpm -qa | grep -i openmanage' or 'dpkg -l | grep -i openmanage'.Affected if OMSA is not installed on the system.
-
Identify installed OMSA versionOn Windows, check registry key HKLM\SOFTWARE\Dell\OpenManage\OMSA\InstalledVersion or view version info in Add/Remove Programs. On Linux, run 'omreport about' or check RPM/DEB package version with 'rpm -qa | grep OpenManage'Affected if The installed version matches one of the affected versions: 9.1, 9.1.0.1, 9.1.0.2, 9.2, 9.2.0.1, or 9.2.0.2.
-
Confirm web service is runningCheck if OMSA web server is active. On Windows, verify the 'Dell OpenManage Server Administrator' service status. On Linux, run 'service dellsrv status' or check for OMSA processes. The web interface typically listens on port 1311.Affected if The OMSA web service (omaws) is running and accessible.
-
Verify web interface accessibilityCheck if the OMSA web port (default 1311) is listening and accessible from the network. Run 'netstat -an | grep 1311' or 'ss -tlnp | grep 1311' to confirm the port is in LISTEN state and review firewall rules.Affected if Port 1311 (or configured OMSA web port) is open and accessible to network attackers.
A system is affected if Dell EMC OpenManage Server Administrator versions 9.1 through 9.2.0.2 are installed with the web service running and accessible.
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.
dbcve · scopedUpgrade OMSA to version 9.1.0.3 or 9.2.0.4 or later to obtain the patch for proper input parameter validation.
9.1.0.3 or 9.2.0.4 (or later)
- 1. Identify the currently installed version of Dell EMC OpenManage Server Administrator by running the version check command or checking the program files.
- 2. Download Dell EMC OpenManage Server Administrator version 9.1.0.3 or version 9.2.0.4 (or later) from the official Dell support website at www.dell.com.
- 3. Back up the current OMSA configuration and any critical data before proceeding with the upgrade.
- 4. Stop the OMSA service using the operating system's service management tools.
- 5. Install the downloaded fixed version by running the installer with appropriate administrative privileges.
- 6. Follow the on-screen installation prompts to complete the upgrade.
- 7. Restart the OMSA service after installation completes.
- 8. Verify the installation was successful by checking the version number matches the fixed release.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2019-3723 — 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-3723 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