CVE-2024-12086: Rsync: path traversal vulnerability in rsync

Published Dec 5, 2024
·
Updated

A flaw was found in rsync. It could allow a server to enumerate the contents of an arbitrary file from the client's machine. This issue occurs when files are being copied from a client to a server. During this process, the rsync server will send checksums of local data to the client to compare with in order to determine what data needs to be sent to the server. By sending specially constructed checksum values for arbitrary files, an attacker may be able to reconstruct the data of those files byte-by-byte based on the responses from the client.

Other sources

A flaw was found in rsync. When using the --safe-links option, the rsync client fails to properly verify if a symbolic link destination sent from the server contains another symbolic link within it. This results in a path traversal vulnerability, which may lead to arbitrary file write outside the desired directory.

— OSV

A heap-based buffer overflow flaw was found in the rsync daemon. This issue is due to improper handling of attacker-controlled checksum lengths (s2length) in the code. When MAXDIGESTLEN exceeds the fixed SUMLENGTH (16 bytes), an attacker can write out of bounds in the sum2 buffer.

— OSV

A path traversal vulnerability exists in rsync. It stems from behavior enabled by the --inc-recursive option, a default-enabled option for many client options and can be enabled by the server even if not explicitly enabled by the client. When using the --inc-recursive option, a lack of proper symlink verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to write files outside of the client's intended destination directory. A malicious server could write malicious files to arbitrary locations named after valid directories/paths on the client.

— OSV

Rsync: rsync server leaks arbitrary client files

— Microsoft

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

— Launchpad

Affected Software

31 affected componentsFixes available
F5 BIG-IQ Centralized Management
Microsoft azl3 rsync 3.2.7-1
Microsoft cbl2 rsync 3.2.5-1
Microsoft cbl2 rsync 3.4.1-1
Microsoft azl3 rsync 3.4.1-1
Samba rsync<=3.3.0
redhat OpenShift Container Platform=4.0
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
redhat Enterprise Linux=10.0
AlmaLinux Almalinux=8.0
AlmaLinux Almalinux=9.0
AlmaLinux Almalinux=10.0
Archlinux Arch Linux
Gentoo Linux
NixOS NixOS<24.11
SUSE SuSE Linux
Tritondatacenter Smartos<20250123
alpine/rsync<3.4.0-r0
3.4.0-r0
alpine/rsync<3.4.0-r0
3.4.0-r0
alpine/rsync<3.4.0-r0
3.4.0-r0
alpine/rsync<3.4.0-r0
3.4.0-r0
alpine/rsync<3.4.0-r0
3.4.0-r0
alpine/rsync<3.4.0-r0
3.4.0-r0
alpine/rsync<3.4.0-r0
3.4.0-r0
debian/rsync<3.2.7-1+deb12u1
3.2.7-1+deb12u1
debian/rsync<3.3.0+ds1-3
3.3.0+ds1-3
debian/rsync<3.3.0+ds1-3
3.3.0+ds1-3
debian/rsync
3.2.7-1+deb12u63.2.7-1+deb12u53.4.1+ds1-5+deb13u43.5.0+ds1-0+deb13u13.5.1+ds1-23.5.2+ds1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/rsync to a version that resolves this vulnerability.

    Fixed in 3.4.0-r0
  2. Upgrade

    Upgrade debian/rsync to a version that resolves this vulnerability.

    Fixed in 3.2.7-1+deb12u1
  3. Upgrade

    Upgrade debian/rsync to a version that resolves this vulnerability.

    Fixed in 3.3.0+ds1-3
  4. Upgrade

    Upgrade debian/rsync to a version that resolves this vulnerability.

    Fixed in 3.2.7-1+deb12u6Fixed in 3.2.7-1+deb12u5Fixed in 3.4.1+ds1-5+deb13u4Fixed in 3.5.0+ds1-0+deb13u1Fixed in 3.5.1+ds1-2Fixed in 3.5.2+ds1-1

Event History

Dec 5, 2024
Data Sourced
via Red Hat·02:39 PM
DescriptionSeverityAffected Software
Jan 14, 2025
CVE Published
via MITRE·05:37 PM
Data Sourced
via MITRE·05:37 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·06:15 PM
Affected Software
Jan 19, 2025
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeaknessAffected Software
Jan 23, 2025
News Published
via BleepingComputer·06:30 PM
Feb 26, 2025
Exploit Published
via CISA·02:14 PM
Mar 13, 2025
Advisory Published
via F5·01:26 AM
Aug 5, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-12086?

CVE-2024-12086 is classified as a medium-severity vulnerability.

2

How do I fix CVE-2024-12086?

To fix CVE-2024-12086, upgrade the rsync package to version 3.2.3-4+deb11u3, 3.2.7-1+deb12u2, or 3.3.0+ds1-4.

3

What does CVE-2024-12086 affect?

CVE-2024-12086 affects versions of the rsync package up to and including 3.2.3-4+deb11u1 and 3.2.7-1.

4

What is the risk of CVE-2024-12086?

The risk of CVE-2024-12086 is that it allows a server to enumerate the contents of arbitrary files from the client's machine.

5

Is CVE-2024-12086 exploitable remotely?

Yes, CVE-2024-12086 can be exploited remotely if the affected rsync server is accessible over the network.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203