Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1491206 - (CVE-2017-12163) CVE-2017-12163 Samba: Server memory information leak over SMB1
CVE-2017-12163 Samba: Server memory information leak over SMB1
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170920,repor...
: Security
Depends On: 1491209 1491210 1491211 1491212 1491213 1491214 1491769 1493441
Blocks: 1488198
  Show dependency treegraph
 
Reported: 2017-09-13 06:28 EDT by Huzaifa S. Sidhpurwala
Modified: 2018-01-24 07:29 EST (History)
16 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An information leak flaw was found in the way SMB1 protocol was implemented by Samba. A malicious client could use this flaw to dump server memory contents to a file on the samba share or to a shared printer, though the exact area of server memory cannot be controlled by the attacker.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2789 normal SHIPPED_LIVE Moderate: samba security update 2017-09-21 14:18:01 EDT
Red Hat Product Errata RHSA-2017:2790 normal SHIPPED_LIVE Moderate: samba security update 2017-09-21 14:06:48 EDT
Red Hat Product Errata RHSA-2017:2791 normal SHIPPED_LIVE Moderate: samba4 security update 2017-09-21 11:51:02 EDT
Red Hat Product Errata RHSA-2017:2858 normal SHIPPED_LIVE Moderate: samba security update 2017-10-04 05:12:56 EDT

  None (edit)
Description Huzaifa S. Sidhpurwala 2017-09-13 06:28:51 EDT
All versions of Samba are vulnerable to a server memory information leak bug over SMB1 if a client can write data to a share. Some SMB1 write requests were not correctly range checked to ensure the client had sent enough data to fulfill the write, allowing server memory contents to be written into the file (or printer) instead of client supplied data. The client cannot control the area of the server memory that is written to the file (or printer).
Comment 1 Huzaifa S. Sidhpurwala 2017-09-13 06:29:00 EDT
Mitigation:

As this is an SMB1-only vulnerability, it can be avoided by setting the server to only use SMB2 via adding:

server min protocol = SMB2_02

to the [global] section of your smb.conf and restarting smbd.
Comment 2 Huzaifa S. Sidhpurwala 2017-09-13 06:29:06 EDT
Acknowledgments:

Name: Yihan Lian and Zhibin Hu (Qihoo 360 Gear Team), Stefan Metzmacher (SerNet), Jeremy Allison (Google)
Comment 5 Huzaifa S. Sidhpurwala 2017-09-20 04:19:08 EDT
External References:

https://www.samba.org/samba/security/CVE-2017-12163.html
Comment 6 Huzaifa S. Sidhpurwala 2017-09-20 04:21:25 EDT
Created samba tracking bugs for this issue:

Affects: fedora-all [bug 1493441]
Comment 7 errata-xmlrpc 2017-09-21 07:51:53 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2017:2791 https://access.redhat.com/errata/RHSA-2017:2791
Comment 8 errata-xmlrpc 2017-09-21 10:07:59 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2017:2790 https://access.redhat.com/errata/RHSA-2017:2790
Comment 9 errata-xmlrpc 2017-09-21 10:19:37 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2017:2789 https://access.redhat.com/errata/RHSA-2017:2789
Comment 10 errata-xmlrpc 2017-10-04 01:14:00 EDT
This issue has been addressed in the following products:

  Red Hat Gluster Storage 3.3 for RHEL 6
  Red Hat Gluster Storage 3.3 for RHEL 7

Via RHSA-2017:2858 https://access.redhat.com/errata/RHSA-2017:2858

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