Red Hat Bugzilla – Bug 472298
CVE-2008-4314 samba: arbitrary memory disclosure
Last modified: 2008-12-03 02:35:07 EST
Quoting the Samba advisory:
Samba 3.0.29 and beyond contain a change to deal with gcc 4
optimizations. Part of the change modified range checking for client-generated
offsets of secondary trans, trans2 and nttrans requests. These requests are
used to transfer arbitrary amounts of memory from clients to servers and back
using small SMB requests and contain two offsets: One offset (A) pointing into
the PDU sent by the client and one (B) to direct the transferred contents into
the buffer built on the server side. While the range checking for offset (B) is
correct, a cut&paste error lets offset (A) pass completely unchecked against
The buffers passed into trans, trans2 and nttrans undergo higher-level
processing like DCE/RPC requests or listing directories. The missing bounds
check means that a malicious client can make the server do this higher-level
processing on arbitrary memory contents of the smbd process handling the
request. It is unknown if that can be abused to pass arbitrary memory contents
back to the client, but an important barrier is missing from the affected Samba
Created attachment 324105 [details]
Proposed upstream patch
Public now via:
Samba 3.0.29 - 3.2.4 (inclusive)
Fixed upstream in:
Samba 3.2.5 and 3.0.33
Upstream patches for 3.2.x and 3.0.x:
This issue did not affect version of Samba as shipped with Red Hat Enterprise Linux 2.1, 3, 4 and 5.
samba-3.2.5-0.22.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
samba-3.2.5-0.23.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
samba-3.0.33-0.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
This issue was addressed in: