CVE-2024-12087

Rsync: path traversal vulnerability in rsync

HIGH
7.5
CVSS Score
Published: January 14, 2025 at 05:57 PM UTC
Updated: October 21, 2026 at 09:17 PM UTC
20 products affected across 9 vendorsEnterprise LinuxEnterprise Linux Server AusEnterprise Linux Eus

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
PoC

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions
All versions
v < 24.11
Affected range stops below 24.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 0:3.0.6-12.el6_10.2 (unaffected)
Vendor states this is fixed in 0:3.1.2-12.el7_9.2 (unaffected)
Vendor states this is fixed in 0:3.1.3-12.el8_4.6 (unaffected)
Vendor states this is fixed in 0:3.1.3-14.el8_6.9 (unaffected)
Vendor states this is fixed in 0:3.1.3-20.el8_8.4 (unaffected)
Vendor states this is fixed in 0:3.1.3-21.el8_10 (unaffected)
Vendor states this is fixed in 0:3.1.3-7.el8_2.6 (unaffected)
Vendor states this is fixed in 0:3.2.3-19.el9_2.2 (unaffected)
Vendor states this is fixed in 0:3.2.3-19.el9_4.2 (unaffected)
Vendor states this is fixed in 0:3.2.3-9.el9_0.4 (unaffected)
Vendor states this is fixed in 0:3.2.5-3.el9 (unaffected)
Vendor states this is fixed in 0:3.4.1-2.el10 (unaffected)

References (20)

Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2025:2600
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2025:7050
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2025:8385
VDB Entryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/security/cve/CVE-2024-12087
Issue Trackingx_refsource_REDHATThird Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2330672
ExploitThird Party Advisory
Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0
https://github.com/google/security-research/security/advisories/GHSA-p5pg-x43v-mvqj
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2025:23154

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card