dbcve.org
Emc Data Domain OsOperating system · Dell

CVE-2016-0912

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-19
Fix available
A fix is available. Upgrade to after 5.7.1.0 or later.
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
EMC Data Domain OS 5.4 through 5.7 before 5.7.2.0 allows remote authenticated users to bypass intended password-change restrictions by leveraging access to (1) a different account with the same role as a target account or (2) an account's session at an unattended workstation.

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

EMC Data Domain OS 5.4 through 5.7 before 5.7.2.0 contains an authentication/authorization bypass vulnerability where remote authenticated users can change passwords for accounts they should not have access to. This is achieved either by leveraging access to a different account with the same role as the target account, or by exploiting an account session left at an unattended workstation.

MitigationUpgrade EMC Data Domain OS to version 5.7.2.0 or later to remediate this vulnerability. Additionally, enforce strict session timeouts and discourage sharing of accounts with identical roles to limit the attack surface.

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.7.1.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
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 Data Domain OS version
    Run command 'version' or 'ddr version' on the Data Domain system, or check the system management interface for the OS version information
    Affected if The installed version is 5.4, 5.5, 5.6, 5.7, or 5.7.1.0 (any version from 5.4 up to and including 5.7.1.0)
  2. Review account role assignments
    List all user accounts and their assigned roles using 'user' or 'show users' command in Data Domain CLI, or check through the management interface
    Affected if Multiple user accounts exist with identical roles (such as multiple admin or operator accounts)
  3. Inspect session timeout configuration
    Check session timeout settings using 'session timeout' or 'show session' command, or examine the system security configuration file
    Affected if Session timeouts are set to very long durations, disabled, or not enforced

A system is affected if it runs Data Domain OS version 5.7.1.0 or earlier and has multiple accounts with shared roles or inadequate session timeout enforcement, allowing unauthorized password modification by an authenticated user with same-role access.

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

Upgrade EMC Data Domain OS to version 5.7.2.0 or later to remediate this vulnerability. Additionally, enforce strict session timeouts and discourage sharing of accounts with identical roles to limit the attack surface.

Recommended fix High confidence

5.7.2.0 or later

  1. 1. Identify the current Data Domain OS version by running `ddboost show version` or checking the system management interface.
  2. 2. Schedule a maintenance window for the upgrade process.
  3. 3. Back up the current Data Domain configuration using the `config` or `ddr config` commands according to EMC best practices.
  4. 4. Download EMC Data Domain OS version 5.7.2.0 or later from the EMC support portal (support.emc.com).
  5. 5. Upload the upgrade image to the Data Domain system using `ddr upgrade` or the management interface.
  6. 6. Initiate the upgrade using `ddr upgrade start` or through the GUI, following the on-screen prompts.
  7. 7. Wait for the upgrade to complete and for the system to reboot automatically.
  8. 8. Verify the new version is installed by running `ddboost show version` or checking the system info.

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

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 the upgrade done

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-2016-0912 — 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-2016-0912 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