CVE-2016-0910
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 Data Domain OS 5.5 before 5.5.4.0, 5.6 before 5.6.1.004, and 5.7 before 5.7.2.0 stores session identifiers of GUI users in a world-readable file, which allows local users to hijack arbitrary accounts via unspecified vectors.
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 Data Domain OS stores GUI session identifiers in a world-readable file, allowing any local user to read session tokens and hijack arbitrary user sessions.
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<= 5.5.3.3<= 5.6.1.0<= 5.7.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Determine Data Domain OS versionRun 'ddr version' or access the system management interface to retrieve the installed Data Domain OS version numberAffected if The installed version is 5.5.3.3 or earlier, 5.6.1.0 or earlier, or 5.7.1.0 or earlier (including any 5.5.x, 5.6.x, or 5.7.x release below the fixed versions)
-
Verify GUI is enabledCheck if the Data Domain GUI management interface is active by accessing the web UI or checking GUI service status via system commandsAffected if The GUI interface is enabled and accessible, as the vulnerability specifically affects GUI session storage
-
Locate session identifier filesSearch for files containing session data or tokens in the Data Domain filesystem, typically in /ddr/var or /ddr/etc directories where application data is storedAffected if Session-related files exist in locations accessible to the local operating system
-
Check file permissions on session storageUse 'ls -la' to inspect permissions on files suspected to contain GUI session identifiersAffected if Any file containing GUI session tokens is readable by all users (permissions include 'other' read permission, such as 644 or 666)
A user is affected if running a Data Domain OS version 5.5.3.3 or lower, 5.6.1.0 or lower, or 5.7.1.0 or lower with the GUI enabled and session files readable by all local users.
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 dataUpgrade to Data Domain OS version 5.5.4.0, 5.6.1.004, or 5.7.2.0 or later which properly secures session data; restrict file permissions as interim measure if patching is delayed.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0910 — 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-2016-0910 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