dbcve.org
GlusterfsApplication · Gluster

CVE-2018-1112

HIGH · 8.8 CVSS v3.0 Published 2018-04-25
Fix available
A fix is available. Upgrade to 3.10.12 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
glusterfs server before versions 3.10.12, 4.0.2 is vulnerable when using 'auth.allow' option which allows any unauthenticated gluster client to connect from any network to mount gluster storage volumes. NOTE: this vulnerability exists because of a CVE-2018-1088 regression.

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 confidence

GlusterFS server versions before 3.10.12 and 4.0.2 contain a regression of CVE-2018-1088 where the 'auth.allow' option incorrectly permits any unauthenticated gluster client from any network to mount storage volumes, allowing complete unauthorized access to stored data.

MitigationUpgrade GlusterFS server to version 3.10.12, 4.0.2 or later and properly restrict the 'auth.allow' option to specific trusted IP addresses or networks instead of using wildcards.

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
GlusterfsApplication
Affected:< 3.10.12= 4.0.2

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine GlusterFS server version
    Run `gluster --version` or check the installed package (e.g., `rpm -q glusterfs-server` or `dpkg -l glusterfs-server`)
    Affected if The installed version is below 3.10.12 or is exactly 4.0.2
  2. Identify configured volumes
    Run `gluster volume list` to see all configured volumes
    Affected if Any volume exists on the affected GlusterFS version
  3. Inspect auth.allow settings
    Run `gluster volume info` for each volume and look for the 'auth.allow' option, or inspect the volume volfile directly
    Affected if The auth.allow option contains wildcard values such as '*', '0.0.0.0/0', or any broad network range that permits unauthenticated access from any IP address

You are affected if your GlusterFS server version is less than 3.10.12 or equals 4.0.2 AND any volume has the auth.allow option configured with permissive wildcard values allowing unrestricted network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.10.12 or later
Fixed in 3.10.12
Interim mitigation

Upgrade GlusterFS server to version 3.10.12, 4.0.2 or later and properly restrict the 'auth.allow' option to specific trusted IP addresses or networks instead of using wildcards.

Fix this in Glusterfs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1112 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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