CVE-2016-0889
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 · uneditedAn HTTP servlet in vApp Manager in EMC Unisphere for VMAX Virtual Appliance before 8.2.0 allows remote attackers to write to arbitrary files via a crafted pathname.
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 confidenceArbitrary file write vulnerability in the vApp Manager HTTP servlet of EMC Unisphere for VMAX Virtual Appliance. Remote unauthenticated attackers can write to arbitrary files on the system via a crafted pathname, leading to potential complete system compromise.
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<= 8.1CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Confirm Unisphere for VMAX Virtual Appliance is deployedIdentify any Virtual Appliance running Unisphere for VMAX in your infrastructure. Check virtual machine inventory or deployment records for systems named 'Unisphere' or 'VMAX' virtual appliance.Affected if The product is not present in your environment.
-
Determine installed Unisphere versionAccess the Unisphere web interface and navigate to the About or Settings page to view the version number. Alternatively, check the virtual appliance's system information or login via SSH and run: cat /opt/emc/unisphere/version or ls -la /opt/emc/unisphere/Affected if Version is 8.1 or lower.
-
Verify vApp Manager servlet is accessibleAttempt to access the vApp Manager endpoint. The vulnerable URL pattern is typically: https://<unisphere-host>/vAppManager/ or http://<unisphere-host>:8443/vAppManager/ . Check if these endpoints respond to HTTP requests.Affected if The vApp Manager servlet responds to requests without authentication.
-
Check management interface network exposureReview firewall rules, network ACLs, or security group configurations to determine if the Unisphere management ports (typically 8443, 443, or 80) are exposed to untrusted networks or the public internet.Affected if The management interface is reachable from untrusted networks without VPN or IP restrictions.
You are affected if Unisphere for VMAX Virtual Appliance version 8.1 or lower is deployed AND the vApp Manager servlet is network-accessible to untrusted users.
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 Unisphere for VMAX Virtual Appliance to version 8.2.0 or later. Until patched, restrict network access to the management interface to trusted sources only.
Unisphere for VMAX Virtual Appliance 8.2.0 or later
- Identify the current version of EMC Unisphere for VMAX Virtual Appliance running in your environment
- Access EMC Support portal and download version 8.2.0 or later of the Unisphere for VMAX Virtual Appliance
- Review EMC's official upgrade documentation for vApp Manager before proceeding
- Follow the documented upgrade procedure to migrate from version 8.1 or earlier to version 8.2.0 or later
- Verify the upgrade was successful by confirming the new version number in the Unisphere interface
- Validate that the vApp Manager service is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0889 — 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-2016-0889 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