Rsync vulnerabilities
openwall.com
Rsync vulnerabilities
1–10 of 27 posts
Re: Rsync vulnerabilities
#2Slackware sent a fixed version of rsync out yesterday.
But I wonder of OpenBSD's openrsync has the same issue ? Or did that version avoid the issues when it was created ?
If it was avoided, seems OpenBSD was ahead of the curve again.
Re: Rsync vulnerabilities
#3Do I read correctly that this is related to "rsync daemon" (rsyncd), and therefore has minimal impact on people who just use rsync over ssh?
Re: Rsync vulnerabilities
#4Do I read correctly that this is related to "rsync daemon" (rsyncd), and therefore has minimal impact on people who just use rsync over ssh?
[dead]
Re: Rsync vulnerabilities
#5Do I read correctly that this is related to "rsync daemon" (rsyncd), and therefore has minimal impact on people who just use rsync over ssh?
My read (not an expert) is that you are safe if your rsync is only via secure connections, to & from systems where untrusted parties can neither run rsync, nor play clever games with the files which rsync is accessing.
Which (in my paranoid opinion) is pretty much the only secure use case anyway, for code like rsync.
Re: Rsync vulnerabilities
#6Do I read correctly that this is related to "rsync daemon" (rsyncd), and therefore has minimal impact on people who just use rsync over ssh?
My reading is that the first two CVEs are with rsync daemon, but the others are more general - I think "rsync server" is meaning the remote rsync process that is started when you use ssh to connect to the remote. Some of them suggest the rsync client (running on your machine) can be coerced to write to unexpected locations by a malicious rsync server specifically crafted to exploit these CVEs. One suggests a malicious rsync server might be able to reconstruct the contents of arbitrary files on the client using requests sent via the rsync protocol.
I guess the main takeaway is to be careful using rsync connections to machines that you don't trust.
Re: Rsync vulnerabilities
#7Do I read correctly that this is related to "rsync daemon" (rsyncd), and therefore has minimal impact on people who just use rsync over ssh?
Every rsync operation (even locally) involves an rsync client and a separate rsync server process.
Re: Rsync vulnerabilities
#8Does this apply to the GPL or BSD codebase?
There are (now) two rsync codebases.
Re: Rsync vulnerabilities
#9Slackware sent a fixed version of rsync out yesterday. But I wonder of OpenBSD's openrsync has the same issue ? Or did that version avoid the issues when it was created ? If it was avoided, seems OpenBSD was ahead of the curve again.
I'm running several Linux distros and package updates to rsync version 3.2.7 have showed up on all of them already. I can't comment on openrsync.
Re: Rsync vulnerabilities
#10Do I read correctly that this is related to "rsync daemon" (rsyncd), and therefore has minimal impact on people who just use rsync over ssh?
It's the same protocol and code implementing it just proxied over SSH instead of a local pipe or unix socket pair. It's a real world issue unless you trust the remote rsync process and the connection with your local user. So basically only SSH between your single-user desktop and same single-user laptop is unimpacted.