Bug 1601657 (CVE-2018-10911) - CVE-2018-10911 glusterfs: Improper deserialization in dict.c:dict_unserialize() can allow attackers to read arbitrary memory
Summary: CVE-2018-10911 glusterfs: Improper deserialization in dict.c:dict_unserialize...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-10911
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: Engineering1607386 Red Hat1607407 Engineering1607717 Engineering1616829 1625079 Engineering1625082 1625089 1625656 Engineering1633291 Engineering1633303
Blocks: Embargoed1601660
TreeView+ depends on / blocked
 
Reported: 2018-07-17 00:38 UTC by Sam Fowler
Modified: 2021-02-16 23:58 UTC (History)
30 users (show)

Fixed In Version: glusterfs 3.12.14, glusterfs 4.1.4
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in dict.c:dict_unserialize function of glusterfs, dic_unserialize function does not handle negative key length values. An attacker could use this flaw to read memory from other locations into the stored dict value.
Clone Of:
Environment:
Last Closed: 2019-06-10 10:32:46 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 0 None None None 2018-09-04 06:24:37 UTC
Red Hat Product Errata RHSA-2018:2608 0 None None None 2018-09-04 06:26:04 UTC
Red Hat Product Errata RHSA-2018:2892 0 None None None 2018-10-09 15:49:06 UTC
Red Hat Product Errata RHSA-2018:3242 0 None None None 2018-10-30 07:52:40 UTC
Red Hat Product Errata RHSA-2018:3470 0 None None None 2018-11-05 14:57:14 UTC

Description Sam Fowler 2018-07-17 00:38:42 UTC
GlusterFS has a deserialization vulnerability in the dict.c:dict_unserialize() function due to the improper handling of negative length values. An attacker could exploit via a crafted serialized dictionary to disclose arbitrary memory locations.

Comment 1 Sam Fowler 2018-07-17 00:38:52 UTC
Acknowledgments:

Name: Michael Hanselmann (hansmi.ch)

Comment 7 Doran Moppert 2018-07-24 06:05:27 UTC
Statement:

This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Comment 10 Siddharth Sharma 2018-09-04 05:43:53 UTC
Created glusterfs tracking bugs for this issue:

Affects: fedora-all [bug 1625079]

Comment 12 errata-xmlrpc 2018-09-04 06:24:25 UTC
This issue has been addressed in the following products:

  Red Hat Gluster Storage 3.4 for RHEL 7
  Native Client for RHEL 7 for Red Hat Storage

Via RHSA-2018:2607 https://access.redhat.com/errata/RHSA-2018:2607

Comment 13 errata-xmlrpc 2018-09-04 06:25:52 UTC
This issue has been addressed in the following products:

  Red Hat Gluster Storage 3.4 for RHEL 6
  Native Client for RHEL 6 for Red Hat Storage

Via RHSA-2018:2608 https://access.redhat.com/errata/RHSA-2018:2608

Comment 14 Siddharth Sharma 2018-09-04 07:56:45 UTC
upstream fix:

https://review.gluster.org/21067

Comment 17 errata-xmlrpc 2018-10-09 15:48:53 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2018:2892 https://access.redhat.com/errata/RHSA-2018:2892

Comment 18 errata-xmlrpc 2018-10-30 07:52:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2018:3242 https://access.redhat.com/errata/RHSA-2018:3242

Comment 19 errata-xmlrpc 2018-11-05 14:56:48 UTC
This issue has been addressed in the following products:

  Red Hat Virtualization 4 for Red Hat Enterprise Linux 7

Via RHSA-2018:3470 https://access.redhat.com/errata/RHSA-2018:3470


Note You need to log in before you can comment on or make changes to this bug.