CVE-2017-8011
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 · uneditedEMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R for SAS Solution Packs (EMC ViPR SRM prior to 4.1, EMC Storage M&R prior to 4.1, EMC VNX M&R all versions, EMC M&R (Watch4Net) for SAS Solution Packs all versions) contain undocumented accounts with default passwords for Webservice Gateway and RMI JMX components. A remote attacker with the knowledge of the default password may potentially use these accounts to run arbitrary web service and remote procedure calls on the affected system.
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 confidenceEMC ViPR SRM and related monitoring products contain undocumented hardcoded accounts with default passwords for Webservice Gateway and RMI JMX components. Attackers with knowledge of these credentials can authenticate remotely and execute arbitrary web service calls and Java Remote Method Invocation (RMI) procedures, effectively gaining full control over affected systems.
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 dataall versions= 4.0.2<= 4.0.2all versionsCVSS 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.1/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 installed product and versionCheck the installed version of Dell EMC ViPR SRM, Storage Monitoring And Reporting, M&R, or VNX Monitoring And Reporting. Look in the product's About or version information panel, or check the installation directory for version files.Affected if The version is Dell Emc Storage Monitoring And Reporting = 4.0.2, Dell Emc Vipr Srm <= 4.0.2, Dell Emc M&R any version, or Dell Emc Vnx Monitoring And Reporting any version.
-
Locate Webservice Gateway configurationSearch for configuration files related to Webservice Gateway in the product installation directory. Look for files named similarly to webservice-gateway, ws-gateway, or containing 'webservice' and 'gateway' in the path.Affected if Configuration files for Webservice Gateway exist and contain hardcoded user credentials.
-
Locate RMI JMX configurationSearch for configuration files related to RMI JMX in the product installation directory. Look for files containing 'jmx', 'rmi', or 'jmx-remoting' in the filename or path.Affected if Configuration files for RMI JMX exist and contain hardcoded user credentials.
-
Inspect for undocumented accountsOpen the identified Webservice Gateway and RMI JMX configuration files and search for user account entries. Look for hardcoded usernames and passwords that are not documented in the product administration guide.Affected if Undocumented user accounts with default passwords are found in the configuration files.
-
Check if affected services are exposedIdentify if Webservice Gateway (typically ports 8443, 9443, or similar SSL ports) and RMI JMX (typically ports 1099, 9010, or custom JMX ports) are listening on network interfaces accessible from outside. Use netstat or similar tools to list listening ports.Affected if Webservice Gateway or RMI JMX services are listening on interfaces accessible from remote networks.
A system is affected if it runs any of the affected product versions and contains the undocumented hardcoded accounts for Webservice Gateway or RMI JMX components, especially if those services are 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.
From vendor dataImmediately identify and change or disable the undocumented default accounts, or upgrade to ViPR SRM 4.1 / Storage M&R 4.1 and later which contain the fix. Network segmentation should restrict access to Webservice Gateway and RMI JMX ports until remediation is complete.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8011 — 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-2017-8011 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