Gluster StorageApplication · Redhat
CVE-2018-14653
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 versions 4.1.4 and 3.12 is vulnerable to a heap-based buffer overflow in the '__server_getspec' function via the 'gf_getspec_req' RPC message. A remote authenticated attacker could exploit this to cause a denial of service or other potential unspecified impact.
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 · moderate confidenceHeap-based buffer overflow in GlusterFS server's '__server_getspec' function, triggered by specially crafted 'gf_getspec_req' RPC message. An authenticated remote attacker can exploit this to cause denial of service or potentially achieve remote code execution on affected GlusterFS servers.
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
>= 3.0.0, <= 3.1.2>= 4.1.0, <= 4.1.4
Debian LinuxOperating system
= 8.0= 9.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux VirtualizationOperating system
= 4.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed GlusterFS package versionRun 'glusterfs --version' or check package manager output with 'rpm -qa | grep gluster' (RHEL) or 'dpkg -l | grep gluster' (Debian)Affected if Version falls within 3.0.0-3.1.2, 4.1.0-4.1.4, or specific Debian/RHEL versions listed in affected products
-
Verify glusterfs-server service is activeRun 'systemctl status glusterfs-server' or check for 'glusterfsd' process with 'ps aux | grep glusterfsd'Affected if The glusterfsd process is running, enabling the server RPC service required for exploitation
-
Confirm server RPC is listening for remote connectionsRun 'ss -tlnp | grep 24007' or check gluster volume info to see if any volumes are started and listening on the management portAffected if The server is listening on port 24007 or has volumes online, exposing the '__server_getspec' function to network clients
-
Check authentication configurationInspect /etc/glusterfs/glusterd.vol or run 'gluster volume get all auth.allow' to see which clients are permittedAffected if Authentication is configured to allow remote attackers (e.g., '*' or untrusted IP ranges), enabling unauthenticated or authenticated exploitation
You are affected if GlusterFS server version is within the vulnerable range AND the glusterfsd service is running and accessible over the network to untrusted clients.
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 versions 4.1.5+/3.12.15+ or apply vendor patches; implement network access controls to limit RPC exposure to trusted clients as compensating control.
Fix this in Gluster Storage
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14653 — 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-14653 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