GlusterFS file access via exposed REST key
Published Mar 19, 2021 · Updated Aug 4, 2024
Credential exposure in Red Hat OpenShift Container Platform 4.2 allows remote authenticated users to obtain a GlusterFS REST key. The basic-user RBAC role permits users who can edit a GlusterFS StorageClass to retrieve its restuserkey value instead of protecting it as a secret. Basic-user permissions and an affected GlusterFS StorageClass are required; the exposed key authenticates to the REST service for reading or modifying files.
Summary
What happened
Credential exposure in Red Hat OpenShift Container Platform 4.2 allows remote authenticated users to obtain a GlusterFS REST key. The basic-user RBAC role permits users who can edit a GlusterFS StorageClass to retrieve its restuserkey value instead of protecting it as a secret. Basic-user permissions and an affected GlusterFS StorageClass are required; the exposed key authenticates to the REST service for reading or modifying files.
The record
- CVE
- CVE-2019-10225
- Published
- Mar 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=atomic-openshift of openshift-4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo