CVE-2018-14653
CVE-2018-14653 Vulnerability Analysis & Exploit Intelligence
The Gluster file system through versions 4.1.4 and 3.12 is vulnerable to a heap-based buffer overflow in the '__server_getspec' function via the 'gf_getspec_req' RPC message. A remote authenticated attacker could exploit this to cause a denial of service or other potential unspecified impact.
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
6.5
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 |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-122
References
7 on the record
- access.redhat.com/errata/RHSA-2018:3431
vendor-advisory, x_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14653
x_refsource_CONFIRM
- lists.debian.org/debian-lts-announce/2018/11/msg00003.html
mailing-list, x_refsource_MLIST
- 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-122other 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.