OpenshiftApplication · Redhat
CVE-2018-1069
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 · uneditedRed Hat OpenShift Enterprise version 3.7 is vulnerable to access control override for container network filesystems. An attacker could override the UserId and GroupId for GlusterFS and NFS to read and write any data on the network filesystem.
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 confidenceOpenShift Enterprise 3.7 contains a flaw in container network filesystem handling that allows UserId and GroupId override for GlusterFS and NFS mounts, bypassing intended access controls and permitting unauthorized read/write access to all data on network filesystems.
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
OpenshiftApplication
= 3.7CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/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.
-
Verify OpenShift Enterprise versionRun 'oc version' or check the openshift-master and openshift-node package versions using 'rpm -qa | grep openshift'Affected if Version is exactly 3.7 (other versions are not affected by this CVE)
-
Identify active storage classesRun 'oc get storageclass' or 'kubectl get storageclass' to list all configured storage classesAffected if Any storage class uses 'glusterfs' or 'nfs' as the provisioner type
-
Check for PersistentVolumes using GlusterFS or NFSRun 'oc get pv -o yaml' and examine the spec section for each persistent volume, looking for 'glusterfs' or 'nfs' in the mount options or volumeHandleAffected if Persistent volumes are backed by GlusterFS or NFS storage
-
Inspect container security contexts for user/group overrideRun 'oc get <resource> -o yaml' for pods/deployments and examine spec.securityContext or spec.containers[].securityContext for runAsUser or runAsGroup settings set to specific numeric valuesAffected if Containers using GlusterFS/NFS mounts have explicit runAsUser or runAsGroup values that could override expected UID/GID restrictions
Environment is affected if running OpenShift Enterprise exactly version 3.7 AND using GlusterFS or NFS storage with containers that have custom security context user/group IDs defined.
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 to a patched version of OpenShift Enterprise; if upgrade is not immediately feasible, restrict or audit access to container network filesystem mounts and implement additional access control layers for GlusterFS and NFS resources.
Fix this in Openshift
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1069 — 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-1069 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