-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blog post about rsync vulnerabilities #736
Merged
Merged
Changes from 3 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
5a01c6d
Create 2025-01-17-rsync-vulnerabilities.md
jonathanspw 9d8653b
Update 2025-01-17-rsync-vulnerabilities.md
jonathanspw 7da844e
Update 2025-01-17-rsync-vulnerabilities.md
jonathanspw 5e799fc
add image
jonathanspw c5788ef
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw 6916993
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw 217799d
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw 5397c74
Update content/blog/2025-01-17-rsync-vulnerabilities.md
bennyvasquez 1069258
Update content/blog/2025-01-17-rsync-vulnerabilities.md
bennyvasquez a36df02
Update content/blog/2025-01-17-rsync-vulnerabilities.md
bennyvasquez 995f06b
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw 45c62c1
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw 6631a3c
update image
jonathanspw 95abcd8
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw 010178e
Update content/blog/2025-01-17-rsync-vulnerabilities.md
jonathanspw File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
--- | ||
title: "Multiple rsync Vulnerabilities Discovered - Mitigation Status" | ||
jonathanspw marked this conversation as resolved.
Show resolved
Hide resolved
|
||
type: blog | ||
author: | ||
name: "Jonathan Wright" | ||
bio: "-" | ||
jonathanspw marked this conversation as resolved.
Show resolved
Hide resolved
|
||
image: /users/jonathan.jpg | ||
date: '2025-01-17' | ||
post: | ||
title: "Multiple rsync Vulnerabilities Discovered - Mitigation Status" | ||
jonathanspw marked this conversation as resolved.
Show resolved
Hide resolved
jonathanspw marked this conversation as resolved.
Show resolved
Hide resolved
|
||
image: | ||
--- | ||
Security researchers at Google, namely Pedro Gallegos, Simon Scannell, and Jasiel Spelman, identified vulnerabilities in both the rsync server and client. The server vulnerabilities ([CVE-2024-12084](https://access.redhat.com/security/cve/CVE-2024-12084) and [CVE-2024-12085](https://access.redhat.com/security/cve/CVE-2024-12085)) can lead to remote code execution (RCE). On the client side, vulnerabilities allow a malicious server to read arbitrary files ([CVE-2024-12086](https://access.redhat.com/security/cve/CVE-2024-12086)), create unsafe symlinks ([CVE-2024-12087](https://access.redhat.com/security/cve/CVE-2024-12087)), and, under certain conditions, overwrite arbitrary files ([CVE-2024-12088](https://access.redhat.com/security/cve/CVE-2024-12088)). Additionally, during the coordinated response to these issues, Aleksei Gorban reported a sixth vulnerability ([CVE-2024-12747](https://access.redhat.com/security/cve/CVE-2024-12747)) related to how the rsync server manages symlinks. | ||
jonathanspw marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
These vulnerabilities were responsibly disclosed to us through the CERT/CC Vulnerability Notes Database, ahead of the [public disclosure](https://www.kb.cert.org/vuls/id/952657) on January 14, 2025. | ||
|
||
# Impact and Mitigation: | ||
|
||
## AlmaLinx rsync Backport Packages | ||
On January 14, 2025 we released updates for our [backported rsync RPMs](https://wiki.almalinux.org/Mirrors.html) - mainly tailored to mirror owners. rsync from this backport repo was at version 3.3.0, which was vulnerable to all 6 CVEs. rsync 3.4.0 was released to address them all, and subsequently 3.4.1 to address regressions discovered in 3.4.0. We updated the repo to 3.4.0 and subsequently 3.4.1. | ||
|
||
#### Vulnerabilitiy Status | ||
* CVE-2024-12084 - Patched | ||
* CVE-2024-12085 - Patched | ||
* CVE-2024-12086 - Patched | ||
* CVE-2024-12087 - Patched | ||
* CVE-2024-12088 - Patched | ||
* CVE-2024-12747 - Patched | ||
|
||
#### Patched Packages | ||
* rsync-3.4.0-1.el8.x86_64.rpm (regressions fixed in rsync-3.4.1-1.el8.x86_64.rpm) | ||
* rsync-3.4.0-1.el9.x86_64.rpm (regressions fixed in rsync-3.4.1-1.el9.x86_64.rpm) | ||
* rsync-3.4.0-1.el8.aarch64.rpm (regressions fixed in rsync-3.4.1-1.el8.aarch64.rpm) | ||
* rsync-3.4.0-1.el9.aarch64.rpm (regressions fixed in rsync-3.4.1-1.el9.aarch64.rpm) | ||
|
||
## AlmaLinux Kitten 10 | ||
On January 14, 2025 we released updated package for AlmaLinux Kitten 10 addressing all six vulnerabilities. At the time of this posting, Red Hat has not patched CentOS Stream 9 or CentOS Stream 10. If Red Hat chooses to only patch some of the vulnerabilities we will continue to carry patches for all of them within AlmaLinux Kitten 10 - a potential deviation from Red Hat. | ||
|
||
#### Vulnerabilitiy Status | ||
* CVE-2024-12084 - Patched | ||
* CVE-2024-12085 - Patched | ||
* CVE-2024-12086 - Patched | ||
* CVE-2024-12087 - Patched | ||
* CVE-2024-12088 - Patched | ||
* CVE-2024-12747 - Patched | ||
|
||
#### Patched Packages | ||
* rsync-3.3.0-6.el10.alma.1.x86_64.rpm | ||
* rsync-3.3.0-6.el10.alma.1.x86_64_v2.rpm | ||
* rsync-3.3.0-6.el10.alma.1.aarch64.rpm | ||
* rsync-3.3.0-6.el10.alma.1.ppc64le.rpm | ||
* rsync-3.3.0-6.el10.alma.1.s390x.rpm | ||
|
||
## AlmaLinux 8 & AlmaLinux 9 | ||
AlmaLinux 8 and AlmaLinux 9 are vulnerable only to 5 of the 6 CVEs - CVE-2024-12085, CVE-2024-12086, CVE-2024-12087, CVE-2024-12088, and CVE-2024-12747. On January 14, 2025 we prepared packages for AlmaLinux 8 and AlmaLinux 9 with plans to release them on January 15, 2025. Red Hat released updates on January 15, 2025 addressing only CVE-2024-12085 which we promptly released for [AlmaLinux 8](https://errata.almalinux.org/8/ALSA-2025-0325.html) and [AlmaLinux 9](https://errata.almalinux.org/9/ALSA-2025-0324.html) as well. Our builds that patch all five vulnerabilities have not been released as of this posting. | ||
|
||
We have patched builds to address all five CVEs but have not released them as of yet. ALESCo is working to decide if we will release these patched builds and carry the patches moving forward if Red Hat does not also patch them. This would be a deviation from Red Hat. If these patches are important to you and your rsync use-cases please [let ALESCo know](https://chat.almalinux.org/almalinux/channels/alesco)! | ||
|
||
#### Vulnerabilitiy Status | ||
* CVE-2024-12084 - Not Affected | ||
* CVE-2024-12085 - Patched | ||
* CVE-2024-12086 - Vulnerable | ||
* CVE-2024-12087 - Vulnerable | ||
* CVE-2024-12088 - Vulnerable | ||
* CVE-2024-12747 - Vulnerable | ||
|
||
#### Patched Packages (CVE-2024-12085) | ||
* rsync-3.1.3-20.el8_10.x86_64.rpm | ||
* rsync-3.1.3-20.el8_10.aarch64.rpm | ||
* rsync-3.1.3-20.el8_10.ppc64le.rpm | ||
* rsync-3.1.3-20.el8_10.s390x.rpm | ||
* rsync-daemon-3.1.3-20.el8_10.x86_64.rpm | ||
* rsync-daemon-3.1.3-20.el8_10.aarch64.rpm | ||
* rsync-daemon-3.1.3-20.el8_10.ppc64le.rpm | ||
* rsync-daemon-3.1.3-20.el8_10.s390x.rpm | ||
* rsync-3.2.3-20.el9_5.1.x86_64.rpm | ||
* rsync-3.2.3-20.el9_5.1.aarch64.rpm | ||
* rsync-3.2.3-20.el9_5.1.ppc64le.rpm | ||
* rsync-3.2.3-20.el9_5.1.s390x.rpm | ||
* rsync-daemon-3.2.3-20.el9_5.1.x86_64.rpm | ||
* rsync-daemon-3.2.3-20.el9_5.1.aarch64.rpm | ||
* rsync-daemon-3.2.3-20.el9_5.1.ppc64le.rpm | ||
* rsync-daemon-3.2.3-20.el9_5.1.s390x.rpm | ||
jonathanspw marked this conversation as resolved.
Show resolved
Hide resolved
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I like this title. Is this preferential or a blocker?
Not set on mine, just not sure I like what you posed :) It seems too basic IMO I guess
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A title update is a blocker, but I'm okay with something else. Yours is too long and technical (I know, technical blog and all, but it still needs to be MUCH shorter and simpler).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "Rsync vulnerabilities - patching status" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works for me. have a new header image.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed capitalization in the title - do you want to do the same for the image?