Impact
previous bug fixes for symlink races in open() calls missed races in other path based system calls like chmod() and chown(). For rsync daemons with "use chroot = no" this allows an attacker with local filesystem access to change permissions, ownership or timestamp on a file outside the exported module.
This impacts the following system calls:
- chmod set_file_attrs() applies the sender-supplied mode
- lchown set_file_attrs() applies the sender-supplied owner
- utimes set_file_attrs() applies the sender-supplied mtime
- rename the central tmp -> final rename in finish_transfer()
- unlink delete or partial-file cleanup
- mkdir create directory entries from the sender's file list
- symlink create symlink entries
- mknod create device entries
- link hard-link from --link-dest basis to destination
- rmdir --delete cleanup
- lstat pre-transfer dest inspection in the generator
Patches
Fixes are in the 3.4.3 release
Workarounds
ensure that "use chroot" is left at the default value of yes
References
https://rsync.samba.org
Impact
previous bug fixes for symlink races in open() calls missed races in other path based system calls like chmod() and chown(). For rsync daemons with "use chroot = no" this allows an attacker with local filesystem access to change permissions, ownership or timestamp on a file outside the exported module.
This impacts the following system calls:
Patches
Fixes are in the 3.4.3 release
Workarounds
ensure that "use chroot" is left at the default value of yes
References
https://rsync.samba.org