Bug 1522875 (CVE-2017-17434) - CVE-2017-17434 rsync: daemon does not check for fnamecmp filenames allowing for access restriction bypass
Summary: CVE-2017-17434 rsync: daemon does not check for fnamecmp filenames allowing f...
Status: CLOSED WONTFIX
Alias: CVE-2017-17434
Product: Security Response
Classification: Other
Component: vulnerability   
(Show other bugs)
Version: unspecified
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20171204,repor...
Keywords: Security
Depends On: 1511414
Blocks: 1515738
TreeView+ depends on / blocked
 
Reported: 2017-12-06 16:07 UTC by Andrej Nemec
Modified: 2018-01-18 11:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-19 16:29:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Andrej Nemec 2017-12-06 16:07:13 UTC
The daemon in rsync 3.1.2, and 3.1.3-development before 2017-11-03, does not check for fnamecmp filenames in the daemon_filter_list data structure (in the recv_files function in receiver.c) and also does 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 allows remote attackers to bypass intended access restrictions.

Upstream patches:

https://git.samba.org/?p=rsync.git;a=commit;h=5509597decdbd7b91994210f700329d8a35e70a1
https://git.samba.org/?p=rsync.git;a=commit;h=70aeb5fddd1b2f8e143276f8d5a085db16c593b9

Comment 1 Andrej Nemec 2017-12-06 16:12:35 UTC
Created rsync tracking bugs for this issue:

Affects: fedora-all [bug 1511414]

Comment 2 Raphael Sanchez Prudencio 2017-12-19 16:30:06 UTC
Statement:

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.


Note You need to log in before you can comment on or make changes to this bug.