FuseApplication · Debian
CVE-2016-1233
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 unspecified udev rule in the Debian fuse package in jessie before 2.9.3-15+deb8u2, in stretch before 2.9.5-1, and in sid before 2.9.5-1 sets world-writable permissions for the /dev/cuse character device, which allows local users to gain privileges via a character device in /dev, related to an ioctl.
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 confidenceThe Debian FUSE package's udev rule incorrectly sets world-writable permissions (0666) on the /dev/cuse character device. This allows any local user to access the device and potentially exploit ioctl calls to gain elevated privileges.
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
FuseApplication
<= 2.9.3-14CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify /dev/cuse device permissionsRun `ls -la /dev/cuse` to check the device file permissionsAffected if The device exists with permissions set to 0666 (world-writable) or any permission allowing read/write access to all users
-
Locate and inspect the cuse udev ruleCheck udev rules in /lib/udev/rules.d/ and /etc/udev/rules.d/ for any file containing 'cuse' - examine the MODE= setting (e.g., `grep -r cuse /lib/udev/rules.d/ /etc/udev/rules.d/`).Affected if The udev rule contains MODE="0666" or similar world-writable setting for the cuse device
-
Check installed fuse package versionRun `dpkg -s fuse` or `dpkg -s fuse2` and look at the Version fieldAffected if The installed version is 2.9.3-14 or earlier (before the fix in 2.9.3-15+deb8u2 for jessie)
-
Confirm udev rule file ownershipRun `ls -la /lib/udev/rules.d/` and check the fuse-related rules files (typically 99-fuse.rules or similar)Affected if A udev rule for cuse exists and is actively applying the vulnerable 0666 permissions
A user is affected if the /dev/cuse device exists with world-writable permissions (0666) or the udev rule grants such permissions, combined with a fuse package version <= 2.9.3-14.
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 dataUpdate the fuse package to the patched version (jessie: 2.9.3-15+deb8u2 or later, stretch: 2.9.5-1 or later), or manually modify the udev rule to restrict permissions to root-only (e.g., 0660 owned by root:disk).
Fix this in Fuse
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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 $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1233 — 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-1233 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