Gluster StorageApplication · Redhat
CVE-2017-15086
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 discovered that the fix for CVE-2017-12151 was not properly shipped in erratum RHSA-2017:2858 for Red Hat Gluster Storage 3.3 for RHEL 6.
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 confidenceA fix for CVE-2017-12151 was intended to be shipped via erratum RHSA-2017:2858 for Red Hat Gluster Storage 3.3 on RHEL 6, but the fix was not properly included in the erratum, leaving the original vulnerability (an access control bypass in Gluster Storage) unpatched.
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.3CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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.
-
Identify Red Hat Gluster Storage versionRun 'rpm -q redhat-gluster-storage' or 'gluster --version' to determine the installed version of Red Hat Gluster StorageAffected if The installed version is exactly 3.3
-
Confirm RHEL 6 platformRun 'cat /etc/redhat-release' to check if the underlying operating system is RHEL 6, since the erratum RHSA-2017:2858 was released for RHEL 6Affected if The system is running RHEL 6 with Gluster Storage 3.3
-
Check if RHSA-2017:2858 is appliedRun 'yum updateinfo list installed | grep RHSA-2017:2858' or 'rpm -q --changelog glusterfs-server | grep -i 2858' to see if the erratum has been appliedAffected if The erratum RHSA-2017:2858 shows as installed or not installed
-
Verify Gluster service status and volume configurationRun 'gluster volume status' and 'gluster volume info' to identify active volumes, as the access control bypass vulnerability (CVE-2017-12151) affects volume access controlsAffected if Any Gluster volumes are configured and accessible on the affected version
A user is affected if they are running Red Hat Gluster Storage 3.3 on RHEL 6, regardless of whether RHSA-2017:2858 is installed, because the original CVE-2017-12151 fix was not properly included in that erratum.
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 dataVerify the current patch level of Red Hat Gluster Storage 3.3 and ensure the correct erratum or patch for CVE-2017-12151 is properly applied, or upgrade to a version where the fix is confirmed to be fully included.
Fix this in Gluster Storage
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15086 — 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-2017-15086 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