Samba would allow unintended write access to files over the network.. =========================================================================Ubuntu Security Notice USN-1802-1 April 16, 2013 samba vulnerability ========================================================================= A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 12.04 LTS Summary: Samba would allow unintended write access to files over the network. Software Description: - samba: SMB/CIFS file, print, and login server for Unix Details: It was discovered that Samba incorrectly handled CIFS share attributes when SMB2 was used. A remote authenticated user could possibly gain write access to certain shares, bypassing the intended permissions. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 12.04 LTS: samba 2:3.6.3-2ubuntu2.6 In general, a standard system update will make all the necessary changes. References: https://ubuntu.com/security/notices/USN-1802-1 CVE-2013-0454 Package Information: https://launchpad.net/ubuntu/+source/samba/2:3.6.3-2ubuntu2.6 . The Samba flaw exposes systems to unauthorized file alterations on Ubuntu, necessitating prompt updates to safeguard the networks.. Samba Vulnerability, File Access, Ubuntu Security. . LinuxSecurity.com Team
New rsync packages are available for Slackware 8.1, 9.0, 9.1, and -current to fix a security issue. When running an rsync server without the chroot option it is possible for an attacker to write outside of the allowed directory. Any sites running rsync in that mode should upgrade right away (and should . -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [slackware-security] rsync update (SSA:2004-124-01) New rsync packages are available for Slackware 8.1, 9.0, 9.1, and -current to fix a security issue. When running an rsync server without the chroot option it is possible for an attacker to write outside of the allowed directory. Any sites running rsync in that mode should upgrade right away (and should probably look into using the chroot option as well). More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database: https://www.cve.org/CVERecord?id=CVE-CAN-2004-0426 Here are the details from the Slackware 9.1 ChangeLog: +--------------------------+ Sun May 2 17:16:41 PDT 2004 patches/packages/rsync-2.6.2-i486-1.tgz: Upgraded to rsync-2.6.2. Rsync before 2.6.1 does not properly sanitize paths when running a read/write daemon without using chroot, allowing remote attackers to write files outside of the module's path. For more details, see: https://www.cve.org/CVERecord?id=CVE-CAN-2004-0426 (* Security fix *) +--------------------------+ Where to find the new packages: +-----------------------------+ Updated package for Slackware 8.1: Updated package for Slackware 9.0: Updated package for Slackware 9.1: Updated package for Slackware -current: MD5 signatures: +-------------+ Slackware 8.1 package: f7702e872e7816dcb6f9b0ba27c3fb61 rsync-2.6.2-i386-1.tgz Slackware 9.0 package: f6ec19791028f4b355bc16d454031204 rsync-2.6.2-i386-1.tgz Slackware 9.1 package: a42dc11056b37c7ddd94f71e4ce20c74 rsync-2.6.2-i486-1.tgz Slackware -current package: 31eb4e17aea2a32a98d4576fab64ab8b rsync-2.6.2-i486-1.tgz Installationinstructions: +------------------------+ If rsync is running as a server, shut it down first. Then, upgrade the packages as root: # upgradepkg rsync-2.6.2-i486-1.tgz Finally, restart the rsync server if needed. +-----+ . Enhance your security against unauthorized write access by updating the rsync package in your Slackware system through the terminal with these commands. Slackware Updates, Rsync Security, Server Configurations. . Severity: Critical. LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.