samba-4.7.3 (Security Release)
|Reported by:||Douglas R. Reno||Owned by:|
New point version
This is a security release in order to address the following defects: o CVE-2017-14746 (Use-after-free vulnerability.) o CVE-2017-15275 (Server heap memory information leak.) ======= Details ======= o CVE-2017-14746: All versions of Samba from 4.0.0 onwards are vulnerable to a use after free vulnerability, where a malicious SMB1 request can be used to control the contents of heap memory via a deallocated heap pointer. It is possible this may be used to compromise the SMB server. o CVE-2017-15275: All versions of Samba from 3.6.0 onwards are vulnerable to a heap memory information leak, where server allocated heap memory may be returned to the client without being cleared. There is no known vulnerability associated with this error, but uncleared heap memory may contain previously used data that may help an attacker compromise the server via other methods. Uncleared heap memory may potentially contain password hashes or other high-value data. For more details and workarounds, please see the security advisories: o https://www.samba.org/samba/security/CVE-2017-14746.html o https://www.samba.org/samba/security/CVE-2017-15275.html Changes since 4.7.2: -------------------- o Jeremy Allison <firstname.lastname@example.org> * BUG 13041: CVE-2017-14746: s3: smbd: Fix SMB1 use-after-free crash bug. * BUG 13077: CVE-2017-15275: s3: smbd: Chain code can return uninitialized memory when talloc buffer is grown.
Note: See TracTickets for help on using tickets.