CVE-2019-3754
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 Unity Operating Environment versions prior to 5.0.0.0.5.116, Dell EMC UnityVSA versions prior to 5.0.0.0.5.116 and Dell EMC VNXe3200 versions prior to 3.1.10.9946299 contain a reflected cross-site scripting vulnerability on the cas/logout page. A remote unauthenticated attacker could potentially exploit this vulnerability by tricking a victim application user to supply malicious HTML or Java Script code to Unisphere, which is then reflected back to the victim and executed by the web browser.
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 confidenceReflected cross-site scripting (XSS) vulnerability in the Unisphere web interface of Dell EMC Unity storage systems. The cas/logout page does not properly sanitize user-supplied input, allowing malicious HTML or JavaScript code to be reflected back to the victim and executed in their browser.
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< 5.0.0.0.5.116< 5.0.0.0.5.116< 3.1.10.9946299CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Unity Operating Environment versionLog into Unisphere web interface and navigate to Settings > About, or use the service CLI command 'uversion' or check /etc/uci-version file via SSHAffected if Version is below 5.0.0.0.5.116
-
Check UnityVSA versionLog into the UnityVSA Unisphere instance and navigate to Settings > About, or run 'uversion' via service CLI over SSHAffected if Version is below 5.0.0.0.5.116
-
Check VNXe3200 firmware versionLog into the VNXe Unisphere web interface and check Settings > About, or access the system via Navisphere CLI and run 'sys_getversion'Affected if Firmware version is below 3.1.10.9946299
-
Verify Unisphere cas/logout endpoint accessibilityAttempt to access the cas/logout page via browser or curl: https://<unisphere-host>/cas/logout?url=<test-value>Affected if The page is accessible and reflects URL parameters without sanitization (response contains unescaped test value)
You are affected if your installed Unity Operating Environment, UnityVSA, or VNXe3200 version is below the fixed versions (5.0.0.0.5.116 for Unity/UnityVSA, 3.1.10.9946299 for VNXe3200) and the Unisphere web interface is reachable.
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 data3.1.10.99462995.0.0.0.5.116
Apply the vendor-supplied updates: upgrade Dell EMC Unity Operating Environment and UnityVSA to version 5.0.0.0.5.116 or later, and VNXe3200 to version 3.1.10.9946299 or later.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3754 — 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-3754 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