Headline
CVE-2014-0178: Samba - Security Announcement Archive
Samba 3.6.6 through 3.6.23, 4.0.x before 4.0.18, and 4.1.x before 4.1.8, when a certain vfs shadow copy configuration is enabled, does not properly initialize the SRV_SNAPSHOT_ARRAY response field, which allows remote authenticated users to obtain potentially sensitive information from process memory via a (1) FSCTL_GET_SHADOW_COPY_DATA or (2) FSCTL_SRV_ENUMERATE_SNAPSHOTS request.
CVE-2014-0178.html:
=========================================================== == Subject: Uninitialized memory exposure. == == CVE ID#: CVE-2014-0178 == == Versions: Samba 3.6.6 - 4.1.7 (inclusive) == == Summary: Samba 3.6.6 to 4.1.7 are affected by a == vulnerability that allows an authenticated == client to retrieve eight bytes of == uninitialized server memory when a == shadow-copy VFS module is enabled. == ===========================================================
=========== Description ===========
In preparing a response to an authenticated FSCTL_GET_SHADOW_COPY_DATA or FSCTL_SRV_ENUMERATE_SNAPSHOTS client request, affected versions of Samba do not initialize 8 bytes of the 16 byte SRV_SNAPSHOT_ARRAY response field. The uninitialized buffer is sent back to the client.
A non-default VFS module providing the get_shadow_copy_data_fn() hook must be explicitly enabled for Samba to process the aforementioned client requests. Therefore, only configurations with “shadow_copy” or “shadow_copy2” specified for the “vfs objects” parameter are vulnerable.
================== Patch Availability ==================
Patches addressing this issue have been posted to:
http://www.samba.org/samba/security/
Samba versions 4.0.18 and 4.1.8 will be released with fixes for this issue. Immediate security releases will not be issued, due to the low severity of the vulnerability.
========== Workaround ==========
To avoid the vulnerability, affected versions can be configured without “shadow_copy” or “shadow_copy2” specified for the “vfs objects” parameter. This is the default configuration.
======= Credits =======
This vulnerability was found and fixed by Christof Schmitt of the Samba team.