CVE Vulnerabilities

CVE-2018-10907

Stack-based Buffer Overflow

Published: Sep 04, 2018 | Modified: Dec 16, 2021
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

It was found that glusterfs server is vulnerable to multiple stack based buffer overflows due to functions in server-rpc-fopc.c allocating fixed size buffers using alloca(3). An authenticated attacker could exploit this by mounting a gluster volume and sending a string longer that the fixed buffer size to cause crash or potential code execution.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

Name Vendor Start Version End Version
Glusterfs Gluster 3.12.0 (including) 3.12.14 (excluding)
Glusterfs Gluster 4.1.0 (including) 4.1.4 (excluding)
Native Client for RHEL 6 for Red Hat Storage RedHat glusterfs-0:3.12.2-18.el6 *
Native Client for RHEL 7 for Red Hat Storage RedHat glusterfs-0:3.12.2-18.el7 *
Red Hat Gluster Storage 3.4 for RHEL 6 RedHat glusterfs-0:3.12.2-18.el6rhs *
Red Hat Gluster Storage 3.4 for RHEL 6 RedHat redhat-release-server-0:6Server-6.10.0.24.el6rhs *
Red Hat Gluster Storage 3.4 for RHEL 6 RedHat redhat-storage-server-0:3.4.0.0-1.el6rhs *
Red Hat Gluster Storage 3.4 for RHEL 7 RedHat glusterfs-0:3.12.2-18.el7rhgs *
Red Hat Gluster Storage 3.4 for RHEL 7 RedHat redhat-release-server-0:7.5-11.el7rhgs *
Red Hat Gluster Storage 3.4 for RHEL 7 RedHat redhat-storage-server-0:3.4.0.0-1.el7rhgs *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat glusterfs-0:3.12.2-18.el7 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat imgbased-0:1.0.29-1.el7ev *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat redhat-release-virtualization-host-0:4.2-7.3.el7 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat redhat-virtualization-host-0:4.2-20181026.0.el7_6 *
Glusterfs Ubuntu bionic *
Glusterfs Ubuntu cosmic *
Glusterfs Ubuntu esm-apps/bionic *
Glusterfs Ubuntu esm-apps/xenial *
Glusterfs Ubuntu trusty *
Glusterfs Ubuntu trusty/esm *
Glusterfs Ubuntu xenial *

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References