CVE-2024-12085VulnerabilityPublished 3 Feb 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 3 Feb 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

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected =3.1.3-7.el8_2.3	Fixed in–

AI-suggested

Red Hat has released an official security update for rsync in Red Hat Enterprise Linux 8.2 (version 3.1.3-7.el8_2.3) that fixes this vulnerability. Users should apply this update promptly to remediate the information leak. Detailed instructions for applying the update are available in the Red Hat advisory and knowledge base article. No additional mitigation steps are indicated or required beyond applying the official patch.

Description

A security vulnerability (CVE-2024-12085) affecting the rsync utility in Red Hat Enterprise Linux 8.2 has been addressed. The flaw involves an information leak caused by uninitialized stack contents. Rsync is a tool used for fast file synchronization and mirroring by sending only differences over the network. Red Hat has issued an important security update to fix this issue in rsync version 3.1.3-7.el8_2.3 for Red Hat Enterprise Linux 8.2.

Impact

The vulnerability results in an information leak through uninitialized stack contents, which could allow an attacker to access sensitive data unintentionally exposed by the rsync process. The Red Hat advisory classifies the impact as Important, indicating a significant security concern but not necessarily critical. There are no reports of active exploitation in the wild.

Summary

The rsync utility in Red Hat Enterprise Linux 8.2 contains a vulnerability identified as CVE-2024-12085, which causes an information leak via uninitialized stack contents. This flaw could potentially expose sensitive data from the stack memory during rsync operations. Red Hat has released a security update (rsync-3.1.3-7.el8_2.3) to address this vulnerability. The advisory rates the impact as Important and provides updated packages to remediate the issue. No CVSS score is provided in the advisory, and no known exploits in the wild have been reported.

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

Affected software

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