Virtualization HostApplication · Redhat
CVE-2018-10914
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 · uneditedIt was found that an attacker could issue a xattr request via glusterfs FUSE to cause gluster brick process to crash which will result in a remote denial of service. If gluster multiplexing is enabled this will result in a crash of multiple bricks and gluster volumes.
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 confidenceA denial of service vulnerability exists in GlusterFS where an attacker can send a specially crafted xattr (extended attribute) request via the FUSE interface, causing the gluster brick process to crash. When gluster multiplexing is enabled, this can cascade to crash multiple bricks and entire gluster volumes.
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
Virtualization HostApplication
= 4.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Debian LinuxOperating system
= 8.0= 9.0>= 3.12.0, < 3.12.14>= 4.1.0, < 4.1.8= 15.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify GlusterFS versionRun 'gluster --version' or check installed package with 'rpm -q glusterfs-server' (RHEL) or 'dpkg -l glusterfs' (Debian)Affected if The installed version falls within 3.12.0 to 3.12.13, or 4.1.0 to 4.1.7
-
Verify FUSE interface is accessibleCheck for FUSE mounts by running 'mount | grep fuse' or look for gluster FUSE processes with 'ps aux | grep gluster | grep fuse'Affected if FUSE mounting is active and exposed to network attackers
-
Confirm gluster multiplexing is enabledRun 'gluster volume info all' and look for 'cluster.brick-multiplexing' setting, or check /etc/glusterfs/glusterd.vol for multiplexing configurationAffected if Brick multiplexing is enabled (this increases cascade failure risk)
Your environment is affected if GlusterFS versions 3.12.0-3.12.13 or 4.1.0-4.1.7 are running with FUSE interface exposed and brick multiplexing enabled.
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 data3.12.144.1.8
Apply the relevant glusterfs security update/patch, or alternatively disable gluster multiplexing and restrict FUSE access via firewall rules to prevent unauthenticated xattr requests.
Fix this in Virtualization Host
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10914 — 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-2018-10914 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