[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#310982: marked as done (smbmount does not honor uid and gid options with 2.4 kernel)



Your message dated Sat, 17 Feb 2007 12:10:10 +0000
with message-id <E1HIOOI-0005PO-OA@ries.debian.org>
and subject line Bug#310982: fixed in kernel-patch-2.4.27-mips 2.4.27-10.sarge4.040815-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: smbfs
Version: 3.0.14a-1
Severity: serious
Justification: break security on upgrade

Hello Debian samba maintainers,

smbmount does not honour the uid and gid option with the sarge 2.4
kernel when the server has 'unix extensions' enabled.

The security problem is that 'unix extension' are not enabled with woody samba
server but are enabled by the upgrade to sarge (since this is the
default). At this point the bug in smbmount on the samba client allow
users on the client to access the samba share with the same permission
they would have on the server disregarding the uid/gid option passed to
smbmount.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-386
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)



--- End Message ---
--- Begin Message ---
Source: kernel-patch-2.4.27-mips
Source-Version: 2.4.27-10.sarge4.040815-2

We believe that the bug you reported is fixed in the latest version of
kernel-patch-2.4.27-mips, which is due to be installed in the Debian FTP archive:

kernel-patch-2.4.27-mips_2.4.27-10.sarge4.040815-2.dsc
  to pool/main/k/kernel-patch-2.4.27-mips/kernel-patch-2.4.27-mips_2.4.27-10.sarge4.040815-2.dsc
kernel-patch-2.4.27-mips_2.4.27-10.sarge4.040815-2.tar.gz
  to pool/main/k/kernel-patch-2.4.27-mips/kernel-patch-2.4.27-mips_2.4.27-10.sarge4.040815-2.tar.gz
mips-tools_2.4.27-10.sarge4.040815-2_i386.deb
  to pool/main/k/kernel-patch-2.4.27-mips/mips-tools_2.4.27-10.sarge4.040815-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 310982@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier <dannf@debian.org> (supplier of updated kernel-patch-2.4.27-mips package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue,  5 Dec 2006 02:23:13 -0700
Source: kernel-patch-2.4.27-mips
Binary: kernel-headers-2.4.27 kernel-image-2.4.27-sb1-swarm-bn mips-tools kernel-image-2.4.27-r4k-kn04 kernel-image-2.4.27-r4k-ip22 kernel-image-2.4.27-xxs1500 kernel-image-2.4.27-r5k-lasat kernel-image-2.4.27-r3k-kn02 kernel-image-2.4.27-r5k-cobalt kernel-image-2.4.27-r5k-ip22
Architecture: i386 source 
Version: 2.4.27-10.sarge4.040815-2
Distribution: stable-security
Urgency: high
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: dann frazier <dannf@debian.org>
Description: 
 kernel-headers-2.4.27 - Header files related to a specific Linux kernel
 kernel-image-2.4.27-r3k-kn02 - Linux kernel binary image
 kernel-image-2.4.27-r4k-ip22 - Linux kernel binary image
 kernel-image-2.4.27-r4k-kn04 - Linux kernel binary image
 kernel-image-2.4.27-r5k-cobalt - Linux kernel binary image
 kernel-image-2.4.27-r5k-ip22 - Linux kernel binary image
 kernel-image-2.4.27-r5k-lasat - Linux kernel binary image
 kernel-image-2.4.27-sb1-swarm-bn - Linux kernel binary image
 kernel-image-2.4.27-xxs1500 - Linux kernel binary image
 mips-tools - mips specific kernel tools
Closes: 310982
Changes: 
 kernel-patch-2.4.27-mips (2.4.27-10.sarge4.040815-2) stable-security; urgency=high
 .
   * Build against kernel-tree-2.4.27-10sarge5:
     * 233_ia64-sparc-cross-region-mappings.diff
       [SECURITY] Prevent cross-region mappings on ia64 and sparc which
       could be used in a local DoS attack (system crash)
       See CVE-2006-4538
     * 234_atm-clip-freed-skb-deref.diff
       [SECURITY] Avoid dereferencing an already freed skb, preventing a
       potential remote DoS (system crash) vector
       See CVE-2006-4997
     * 235_ppc-alignment-exception-table-check.diff
       [SECURITY][ppc] Avoid potential DoS which can be triggered by some
       futex ops
       See CVE-2006-5649
     * 236_s390-uaccess-memleak.diff
       [SECURITY][s390] Fix memory leak in copy_from_user by clearing the
       remaining bytes of the kernel buffer after a fault on the userspace
       address in copy_from_user()
       See CVE-2006-5174
     * 237_smbfs-honor-mount-opts.diff
       Honor uid, gid and mode mount options for smbfs even when unix extensions
       are enabled (closes: #310982)
       See CVE-2006-5871
     * 238_ppc-hid0-dos.diff
       [SECURITY] [ppc] Fix local DoS by clearing HID0 attention enable on
       PPC970 at boot time
       See CVE-2006-4093
Files: 
 bab2d60567d5858c019407cca58d6688 16632 devel optional mips-tools_2.4.27-10.sarge4.040815-2_i386.deb
 e9154cdadd12cf9d3042fc3c69906796 309221 devel optional kernel-patch-2.4.27-mips_2.4.27-10.sarge4.040815-2.tar.gz
 007ebb5db36532e0bef9462411d7a25b 1051 devel optional kernel-patch-2.4.27-mips_2.4.27-10.sarge4.040815-2.dsc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFeFNqhuANDBmkLRkRAlbcAJ9y2TP8Ebg6geJbHmIgjgA65gTZAwCgluIH
ybe6imjTlNDcs14tWYRvruA=
=Mnjw
-----END PGP SIGNATURE-----


--- End Message ---

Reply to: