Summary
This update for rsync fixes the following issues:
Security issues fixed:
- CVE-2017-17434: The daemon in rsync did not check for fnamecmp filenames in
the daemon_filter_list data structure (in the recv_files function in
receiver.c) and also did not apply the sanitize_paths protection mechanism to
pathnames found in 'xname follows' strings (in the read_ndx_and_attrs function
in rsync.c), which allowed remote attackers to bypass intended access
restrictions' (bsc#1071460).
- CVE-2017-17433: The recv_files function in receiver.c in the daemon in rsync,
proceeded with certain file metadata updates before checking for a filename in
the daemon_filter_list data structure, which allowed remote attackers to bypass
intended access restrictions (bsc#1071459).
- CVE-2017-16548: The receive_xattr function in xattrs.c in rsync did not check
for a trailing '\\0' character in an xattr name, which allowed remote attackers
to cause a denial of service (heap-based buffer over-read and application
crash) or possibly have unspecified other impact by sending crafted data to the
daemon (bsc#1066644).
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 | rsync | 3.0.4-2.53.3.1 |
| SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 | rsync | 3.0.4-2.53.3.1 |
Vulnerabilities 3
-
Unscored —
The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' characte…
-
Unscored —
The recv_files function in receiver.c in the daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, proceeds w…
-
Unscored —
The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemon…