CVE-2016-9869
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 · uneditedAn issue was discovered in EMC ScaleIO versions before 2.0.1.1. Incorrect permissions on the SCINI driver may allow a low-privileged local attacker to modify the configuration and render the ScaleIO Data Client (SDC) server unavailable.
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 confidenceIn EMC ScaleIO versions before 2.0.1.1, the SCINI kernel driver has incorrect file permissions that allow low-privileged local users to modify its configuration. This permission misconfiguration can be exploited to alter driver settings and cause a denial of service on the ScaleIO Data Client (SDC) server.
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<= 2.0.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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Confirm ScaleIO installation and versionRun 'rpm -qa | grep -i scaleio' or check installed packages to identify ScaleIO version. Alternatively, check /opt/emc/scaleio for installation directory and look for version information in release files.Affected if ScaleIO version is 2.0.1.0 or earlier (versions before 2.0.1.1)
-
Locate the SCINI kernel driverSearch for the SCINI driver file using 'find / -name "*scini*" -o -name "*SCINI*" 2>/dev/null' or check standard kernel driver locations under /lib/modules/$(uname -r).Affected if SCINI driver file exists on the system
-
Inspect SCINI driver file permissionsRun 'ls -la' on the identified SCINI driver file to view owner, group, and permission bits (e.g., chmod octal values).Affected if Permissions allow write access (w) for non-owner users or non-root groups (e.g., world-writable or group-writable with low-privileged group membership)
-
Verify if low-privileged users can modify driverAs a non-privileged user attempt to verify write access using 'test -w <scini_driver_path> && echo writable' or check group ownership and membership.Affected if Non-privileged users can write to or modify the SCINI driver configuration files
A system is affected if ScaleIO version is 2.0.1.0 or earlier AND the SCINI kernel driver file permissions allow modification by non-privileged (non-root) 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 ScaleIO version 2.0.1.1 or later which corrects the SCINI driver permissions. Alternatively, review and harden file permissions on the SCINI driver to restrict modification to privileged users only.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9869 — 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-9869 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