dbcve.org
Vnx2 FirmwareOperating system · Emc

CVE-2017-4984

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 VNX2 versions prior to OE for File 8.1.9.211 and VNX1 versions prior to OE for File 7.1.80.8, an unauthenticated remote attacker may be able to elevate their permissions to root through a command injection. This may potentially be exploited by an attacker to run arbitrary code with root-level privileges on the targeted VNX Control Station system, aka remote code execution.

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

Unauthenticated remote command injection in EMC VNX1 and VNX2 Control Station allows attackers to execute arbitrary commands with root privileges. The vulnerability exists in the OE for File components prior to versions 8.1.9.211 (VNX2) and 7.1.80.8 (VNX1), enabling pre-auth RCE at root level.

MitigationUpgrade VNX2 systems to OE for File 8.1.9.211 or later, and VNX1 systems to OE for File 7.1.80.8 or later. If patching is immediately infeasible, restrict network access to the Control Station management interfaces via firewall rules.

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
Vnx2 FirmwareOperating system
Affected:all versions
Vnx1 FirmwareOperating system
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
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 checks

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

  1. Identify EMC VNX model
    Access the Control Station or use the EMC Navisphere CLI to determine if the system is VNX1 or VNX2 hardware
    Affected if System is EMC VNX1 or VNX2 hardware
  2. Check OE for File version on VNX2
    Log into the Control Station and run 'naviseccli -getagent' or check /etc/nvpf_version to retrieve the OE for File version. For VNX2, compare against the vulnerable threshold: versions prior to 8.1.9.211 are affected.
    Affected if OE for File version is below 8.1.9.211 on a VNX2 system
  3. Check OE for File version on VNX1
    Log into the Control Station and run 'naviseccli -getagent' or check /etc/nvpf_version to retrieve the OE for File version. For VNX1, compare against the vulnerable threshold: versions prior to 7.1.80.8 are affected.
    Affected if OE for File version is below 7.1.80.8 on a VNX1 system
  4. Verify Control Station network accessibility
    Confirm whether the Control Station management interface (ports 443, 80, or 22) is exposed to untrusted networks. Check firewall rules and network segmentation configurations.
    Affected if Control Station is accessible from untrusted networks and version is below the fixed releases

A system is affected if it is an EMC VNX1 or VNX2 with OE for File version below 7.1.80.8 (VNX1) or 8.1.9.211 (VNX2) AND the Control Station interface is network-accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade VNX2 systems to OE for File 8.1.9.211 or later, and VNX1 systems to OE for File 7.1.80.8 or later. If patching is immediately infeasible, restrict network access to the Control Station management interfaces via firewall rules.

Recommended fix High confidence

VNX2: OE for File 8.1.9.211 or later; VNX1: OE for File 7.1.80.8 or later

  1. 1. Identify the current VNX firmware version by accessing the Control Station or using the 'naviseccli' command: 'naviseccli -getvcrecversion'
  2. 2. Determine if the system is VNX1 or VNX2 by checking the hardware model
  3. 3. For VNX2 systems: Plan upgrade to OE for File version 8.1.9.211 or later
  4. 4. For VNX1 systems: Plan upgrade to OE for File version 7.1.80.8 or later
  5. 5. Review EMC VNX upgrade documentation and release notes for prerequisites and procedures
  6. 6. Schedule maintenance window as upgrades require system downtime
  7. 7. Perform backup of critical data and configuration settings
  8. 8. Apply the firmware upgrade following EMC documentation procedures
Caveat Review EMC upgrade documentation for compatibility requirements, as firmware upgrades may require specific pre-requisite updates and may have compatibility implications with connected systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vnx2 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
34.0 hours of engineering $5,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-4984 — 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-4984 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