CVE-2018-14654
CVE-2018-14654 Vulnerability Analysis & Exploit Intelligence
The Gluster file system through version 4.1.4 is vulnerable to abuse of the 'features/index' translator. A remote attacker with access to mount volumes could exploit this via the 'GF_XATTROP_ENTRY_IN_KEY' xattrop to create arbitrary, empty files on the target server.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
5.4
MEDIUM
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 5.4 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-22
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /index'.
References
6 on the record
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14654
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:3431
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:3432
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:3470
vendor-advisory, x_refsource_REDHAT
- security.gentoo.org/glsa/201904-06
vendor-advisory, x_refsource_GENTOO
- lists.debian.org/debian-lts-announce/2021/11/msg00000.html
mailing-list, x_refsource_MLIST
Elsewhere on this site
- the gluster projectevery CVE for this vendor
- CWE-22other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.