Bug 1536661 (CVE-2018-5764) - CVE-2018-5764 rsync: sanitization bypass in parse_argument in options.c
Summary: CVE-2018-5764 rsync: sanitization bypass in parse_argument in options.c
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2018-5764
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1536662 1540312
Blocks: 1536665
TreeView+ depends on / blocked
 
Reported: 2018-01-19 20:57 UTC by Laura Pardo
Modified: 2019-09-29 14:30 UTC (History)
10 users (show)

Fixed In Version: rsync 3.1.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-30 18:38:13 UTC


Attachments (Terms of Use)

Description Laura Pardo 2018-01-19 20:57:42 UTC
A flaw was found in rsync verions before 3.1.3. The parse_argument function in options.c in rsyncd component does not prevent multiple --protect-args uses. Thus letting the user to specify the arg in the protected-arg list and shortcut some of the arg-sanitizing code. This vulnerability allows remote attackers to bypass the argument-sanitization protection mechanism, which may lead to a privilege escalation vulnerability.


References:
https://download.samba.org/pub/rsync/src-previews/rsync-3.1.3pre1-NEWS

Patch:
https://git.samba.org/rsync.git/?p=rsync.git;a=commit;h=7706303828fcde524222babb2833864a4bd09e07

Comment 1 Laura Pardo 2018-01-19 20:58:34 UTC
Created rsync tracking bugs for this issue:

Affects: fedora-all [bug 1536662]

Comment 3 Pedro Yóssis Silva Barbosa 2018-01-30 18:37:46 UTC
Statement:

This issue affects the versions of rsync as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. 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.