dbcve.org
Emc M\&rApplication · Dell

CVE-2017-8007

HIGH · 8.8 CVSS v3.1 Published 2017-09-22
Fix available
A fix is available. Upgrade to after 4.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
In EMC ViPR SRM, Storage M&R, VNX M&R, and M&R (Watch4Net) for SAS Solution Packs, the Webservice Gateway is affected by a directory traversal vulnerability. Attackers with knowledge of Webservice Gateway credentials could potentially exploit this vulnerability to access unauthorized information, and modify or delete data, by supplying specially crafted strings in input parameters of the web service call.

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 confidence

Directory traversal vulnerability in EMC ViPR SRM and related products' Webservice Gateway allows authenticated attackers to use specially crafted strings in web service input parameters to access unauthorized files and potentially modify or delete data outside the intended directory.

MitigationImplement strict input validation and path sanitization on all web service parameters to reject directory traversal sequences (e.g., ../). Consider implementing additional access controls and parameter bounds checking.

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
Emc M\&rApplication
Affected:all versions
Emc Storage Monitoring And ReportingApplication
Affected:all versions
Emc Vipr SrmApplication
Affected:<= 4.0.2
Emc Vnx Monitoring And ReportingApplication
Affected:all versions

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed EMC ViPR SRM or related products
    Check system inventory or installed software for presence of: Dell EMC ViPR SRM, Dell EMC M&R, Dell EMC Storage Monitoring and Reporting, or Dell EMC VNX Monitoring and Reporting. Look for associated service processes or web service components.
    Affected if Any of the affected products (ViPR SRM, M&R, Storage Monitoring and Reporting, or VNX Monitoring and Reporting) are installed and the Webservice Gateway component is accessible.
  2. Determine ViPR SRM version
    If ViPR SRM is installed, check the installed version through the product's about page, version file, or administrative console. Compare against the affected range: version 4.0.2 or earlier.
    Affected if ViPR SRM version is 4.0.2 or lower, and the Webservice Gateway is exposed.
  3. Confirm Webservice Gateway is enabled
    Check product configuration or running services for the Webservice Gateway component. Look for exposed web service endpoints (typically on port 8443, 443, or 8080 depending on deployment).
    Affected if The Webservice Gateway service is running and network-accessible.
  4. Review web service input parameter handling
    Examine web service configuration files or proxy settings for input validation mechanisms on web service parameters. Look for whether parameter validation includes directory traversal sequence checks.
    Affected if Web service parameters accept user input without strict validation that blocks traversal sequences like ../ or ..\.

A user is affected if they have any of the affected products (ViPR SRM ≤4.0.2, M&R, Storage Monitoring and Reporting, or VNX Monitoring and Reporting) installed with the Webservice Gateway enabled and accessible without proper input sanitization on web service parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.0.2
Interim mitigation

Implement strict input validation and path sanitization on all web service parameters to reject directory traversal sequences (e.g., ../). Consider implementing additional access controls and parameter bounds checking.

Fix this in Emc M\&r Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8007 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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