LiveActive security incident?Get immediate response
CVE Record

CVE-2024-12086: Rsync: rsync server leaks arbitrary client files

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.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-12086 is an rsync confidentiality flaw. If a user or automated job uploads files to a malicious or compromised rsync server, that server may infer other files from the client system. This is not listed as actively exploited in KEV. Business urgency depends on whether rsync clients push data to untrusted or externally operated servers.

Executive priority

Treat as a targeted confidentiality risk, not a broad emergency. Prioritize backup, deployment, and file-transfer systems that upload to external or shared rsync servers. Patch or restrict those workflows first, especially where sensitive client-side files may exist on the sending host.

Technical view

The issue occurs during client-to-server rsync transfers. A server can send specially constructed checksum values for arbitrary client-side files and use client responses to reconstruct file contents byte by byte. CVSS is 6.1, medium, with high confidentiality impact, high attack complexity, and required user interaction.

Likely exposure

Most exposed environments are those where rsync clients push data to servers outside direct administrative control. The bundle identifies affected Red Hat rsync packages in RHEL 8, 9, 10, RHEL 9.6 EUS, OpenShift Container Platform 4 RHCOS, and Red Hat Discovery 2. RHEL 6 and 7 status is listed as unknown.

Exploitation context

Exploitation requires the client to interact with an attacker-controlled or compromised rsync server during an upload workflow. The source bundle includes a Google Security Research advisory, but KEV is false and the provided sources do not establish active exploitation in the wild.

Researcher notes

The core trust boundary is reversed: a malicious server influences client checksum comparison during uploads. Avoid publishing exploit procedures. Useful analysis areas include identifying client upload paths, server trust assumptions, affected package lineage, and whether vendor fixes alter checksum validation behavior.

Mitigation direction

  • Apply vendor rsync updates or advisories where available for your operating system and platform.
  • Review Red Hat, Debian, NetApp, and upstream guidance for product-specific remediation.
  • Avoid pushing rsync data to untrusted or externally controlled servers until remediated.
  • Restrict automated rsync jobs to trusted destinations with strong access controls.
  • Prioritize systems handling sensitive files or credentials during rsync upload workflows.

Validation and detection

  • Inventory systems with rsync installed and identify package versions.
  • Find scheduled jobs or services that push files to rsync servers.
  • Map rsync destinations to trusted, internal, third-party, or unknown ownership.
  • Check affected Red Hat, Debian, NetApp, and OpenShift assets against vendor advisories.
  • Confirm remediation by verifying installed package versions against vendor guidance.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-390: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-12086 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N1.64redhat

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2024-12086Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineredhat

    Reported to Red Hat.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorrsyncrsync, 0unaffected
Red HatRed Hat Enterprise Linux 10rsync, 0:3.4.1-2.el10affected
Red HatRed Hat Enterprise Linux 9rsync, 0:3.2.5-7.el9_8affected
Red HatRed Hat Enterprise Linux 9rsync, 0:3.2.5-7.el9_8affected
Red HatRed Hat Enterprise Linux 9.6 Extended Update Supportrsync, 0:3.2.5-3.el9_6.1affected
Red HatRed Hat Discovery 2discovery/discovery-ui-rhel9, 1782166952affected
Red HatRed Hat Enterprise Linux 6rsyncunknown
Red HatRed Hat Enterprise Linux 7rsyncunknown
Red HatRed Hat Enterprise Linux 8rsyncaffected
Red HatRed Hat OpenShift Container Platform 4rhcosaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-390 · source CWE mapping

Detection of Error Condition Without Action

Detection of Error Condition Without Action represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.