dbcve.org
Emc Data Domain OsOperating system · Dell

CVE-2017-4983

MEDIUM · 6.7 CVSS v3.0 Published 2017-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
EMC Data Domain OS 5.2 through 5.7 before 5.7.3.0 and 6.0 before 6.0.1.0 is affected by a privilege escalation vulnerability that may potentially be exploited by attackers to compromise 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 · moderate confidence

EMC Data Domain OS contains a privilege escalation vulnerability affecting versions 5.2 through 5.7 before 5.7.3.0 and version 6.0 before 6.0.1.0. The vulnerability allows authenticated attackers to elevate privileges beyond their assigned permissions, potentially compromising the affected storage system.

MitigationUpgrade EMC Data Domain OS to version 5.7.3.0 or 6.0.1.0 or later to remediate this vulnerability.

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 Data Domain OsOperating system
Affected:= 5.2= 5.4= 5.5= 5.6= 5.7= 6.0

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

CVSS:3.0/AV:L/AC:L/PR:H/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 Data Domain OS version
    Run the command to display the OS version (e.g., `software version`, `system show version`, or check version files in system configuration directories)
    Affected if The installed version is 5.2, 5.4, 5.5, 5.6, 5.7, or 6.0 (before 5.7.3.0 or 6.0.1.0 respectively)
  2. Verify version is within affected range
    Compare the identified version against the vulnerable ranges: 5.2 through 5.7 (before 5.7.3.0) or version 6.0 (before 6.0.1.0)
    Affected if The version matches any of the affected versions listed (5.2, 5.4, 5.5, 5.6, 5.7, or 6.0)
  3. Confirm user authentication is enabled
    Check if local or remote user accounts are configured on the Data Domain system (review user management settings or authentication configuration files)
    Affected if User authentication is active and non-administrator accounts exist on the system

Your system is affected if it runs Data Domain OS version 5.2 through 5.7 before 5.7.3.0 or version 6.0 before 6.0.1.0, and has authenticated user accounts configured.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade EMC Data Domain OS to version 5.7.3.0 or 6.0.1.0 or later to remediate this vulnerability.

Fix this in Emc Data Domain Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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