CVE-2024-12085VulnerabilityPublished 15 Jan 2025Updated 10 Nov 2026

Red Hat Security Advisory: rsync security update

Affects Red Hat rsyncSource GCVE Database

Compare

Not known to be exploited.

Data as of 10 Nov 2026, 05:57 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	7.5

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released updated rsync packages that fix this vulnerability. Users of Red Hat Enterprise Linux 8 and its extended life cycle versions should apply the security update as detailed in the Red Hat advisory RHSA-2025:0325. Instructions for applying the update are available at https://access.redhat.com/articles/11258. No additional mitigation steps are required beyond applying the official patch.

Description

A security vulnerability (CVE-2024-12085) in the rsync utility used by Red Hat Enterprise Linux 8 allows information leakage via uninitialized stack contents. Rsync is a file synchronization and mirroring tool that optimizes data transfer by sending only file differences. This flaw could potentially expose sensitive information from memory. Red Hat has issued an important security update addressing this issue for multiple architectures and extended life cycle versions of RHEL 8.

Impact

The vulnerability allows information disclosure via uninitialized stack contents in the rsync utility, potentially exposing sensitive data during file synchronization or mirroring operations. The impact is rated as Important by Red Hat, indicating a significant security concern but not necessarily enabling remote code execution or system compromise. There are no known exploits in the wild at this time.

Summary

The rsync utility in Red Hat Enterprise Linux 8 contains a vulnerability identified as CVE-2024-12085, which causes information leakage through uninitialized stack contents. This flaw could allow an attacker to obtain sensitive data from the stack memory during rsync operations. Red Hat has released updated rsync packages for various architectures including x86_64, s390x, ppc64le, and aarch64, as well as for extended life cycle versions 8.10. The advisory rates the security impact as Important and provides updated packages to remediate the issue.

CWE-908Use of Uninitialized Resource (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses or accesses a resource that has not been initialized.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 10 Nov 2026, 05:57 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-908

Technical details

References

Community reviews

Related threats