CVE-2016-6646
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 · uneditedThe vApp Managers web application in EMC Unisphere for VMAX Virtual Appliance 8.x before 8.3.0 and Solutions Enabler Virtual Appliance 8.x before 8.3.0 allows remote attackers to execute arbitrary code via crafted input to the (1) GetSymmCmdRequest or (2) RemoteServiceHandler class.
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 confidenceThe vApp Managers web application in EMC Unisphere for VMAX Virtual Appliance and Solutions Enabler Virtual Appliance versions prior to 8.3.0 contains a code injection vulnerability in the GetSymmCmdRequest and RemoteServiceHandler classes. Remote unauthenticated attackers can send specially crafted input to these classes to execute arbitrary code on the underlying system.
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.0= 8.1= 8.1.2= 8.2= 8.0= 8.0.3= 8.1= 8.1.2= 8.3= 8.0.3CVSS 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.
-
Identify the installed Unisphere versionAccess the web UI login page or admin console of the Virtual Appliance and locate the version information, typically displayed on the login screen or in System > About/Information settingsAffected if The displayed version matches 8.0, 8.1, 8.1.2, or 8.2 for Dell EMC Unisphere, or 8.0.3 for EMC Unisphere
-
Identify the installed Solutions Enabler versionAccess the Solutions Enabler Virtual Appliance web interface or CLI and retrieve the version number from the admin or system information pageAffected if The displayed version matches 8.0, 8.0.3, 8.1, 8.1.2, or 8.3 for EMC Solutions Enabler
-
Confirm the vApp Manager web application is exposedAttempt to access the web management interface via the appliance IP or hostname on the typical management ports (HTTPS port 443 or 8443)Affected if The Unisphere or Solutions Enabler web interface is reachable over the network
-
Check if RemoteServiceHandler endpoint is accessibleProbe the web application for the RemoteServiceHandler class endpoint using a tool like curl or browser developer tools to see if the path responds (e.g., /symmwin/RemoteServiceHandler or similar vApp Manager paths)Affected if The endpoint returns an HTTP response, indicating the vulnerable class is exposed
-
Verify the appliance is running as a Virtual ApplianceConfirm the environment is a VMAX Virtual Appliance or Solutions Enabler Virtual Appliance by checking the system type in the web UI or CLIAffected if The appliance is identified as a VMAX Virtual Appliance or Solutions Enabler Virtual Appliance
You are affected if your installed version of EMC Unisphere or Solutions Enabler Virtual Appliance is any of 8.0, 8.0.3, 8.1, 8.1.2, 8.2, or 8.3 and the web management interface is network-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 EMC Unisphere for VMAX Virtual Appliance and Solutions Enabler Virtual Appliance to version 8.3.0 or later to remediate this vulnerability. Until patching is feasible, restrict network access to the management interfaces via firewall rules or network segmentation.
8.3.0 or later
- Identify the specific EMC product affected (Unisphere for VMAX Virtual Appliance or Solutions Enabler Virtual Appliance)
- Check the currently installed version of the vApp Manager web application
- Upgrade the affected virtual appliance to version 8.3.0 or later
- After upgrade, verify the vApp Manager web application is running the patched version
- Confirm that the GetSymmCmdRequest and RemoteServiceHandler endpoints no longer accept arbitrary code via crafted input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6646 — 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-6646 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