Gluster StorageApplication · Redhat
CVE-2018-14654
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 · uneditedThe Gluster file system through version 4.1.4 is vulnerable to abuse of the 'features/index' translator. A remote attacker with access to mount volumes could exploit this via the 'GF_XATTROP_ENTRY_IN_KEY' xattrop to create arbitrary, empty files on the target server.
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 confidenceGlusterFS through version 4.1.4 contains a vulnerability in the 'features/index' translator that allows remote attackers with mount access to create arbitrary empty files on the target server via the 'GF_XATTROP_ENTRY_IN_KEY' xattrop operation.
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
Gluster StorageApplication
<= 4.1.4
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux VirtualizationOperating system
= 4.0
VirtualizationApplication
= 4.0
Virtualization HostApplication
= 4.0
Debian LinuxOperating system
= 9.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Check installed GlusterFS versionRun command: glusterfs --version or rpm -q glusterfs-serverAffected if The installed version is 4.1.4 or earlier (or unknown/unspecified) from the affected product list (Redhat Gluster Storage <= 4.1.4, Redhat Enterprise Linux 6.0/7.0, Debian 9.0)
-
Identify volumes using the features/index translatorRun: gluster volume list and for each volume inspect the translator graph with: gluster volume info <volumename> | grep -i index, or check volume configuration files in /var/lib/glusterd/vols/Affected if Any volume has the 'features/index' translator enabled or listed in its configuration
-
Verify mount access controlsReview /etc/glusterfs/glusterd.vol or volume-specific export settings to identify which clients/hosts have mount access, and check for any auth allow/reject settingsAffected if Untrusted or unauthenticated users have mount access to affected volumes
A system is affected if it runs a vulnerable GlusterFS version (4.1.4 or earlier) AND has the features/index translator enabled on any volume that can be accessed by untrusted 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 GlusterFS to version 4.1.5 or later, or disable the 'features/index' translator if not required; also restrict mount access to trusted users.
Fix this in Gluster Storage
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14654 — 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-14654 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