CVE-2024-47569: Insertion of Sensitive Information Into Sent Data Vulnerability in csfd daemon

Published Oct 14, 2025
·
Updated

A insertion of sensitive information into sent data vulnerability in Fortinet FortiMail 7.4.0 through 7.4.2, FortiMail 7.2.0 through 7.2.6, FortiMail 7.0 all versions, FortiManager 7.6.0 through 7.6.1, FortiManager 7.4.1 through 7.4.3, FortiManager Cloud 7.4.1 through 7.4.3, FortiNDR 7.6.0 through 7.6.1, FortiNDR 7.4.0 through 7.4.8, FortiNDR 7.2 all versions, FortiNDR 7.1 all versions, FortiNDR 7.0 all versions, FortiNDR 1.5 all versions, FortiOS 7.6.0, FortiOS 7.4.0 through 7.4.4, FortiOS 7.2.0 through 7.2.8, FortiOS 7.0.0 through 7.0.15, FortiOS 6.4.0 through 6.4.15, FortiOS 6.2 all versions, FortiOS 6.0 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.4.0 through 7.4.4, FortiProxy 7.2.0 through 7.2.10, FortiProxy 7.0 all versions, FortiProxy 2.0 all versions, FortiProxy 1.2 all versions, FortiProxy 1.1 all versions, FortiProxy 1.0 all versions, FortiRecorder 7.2.0 through 7.2.1, FortiRecorder 7.0.0 through 7.0.4, FortiTester 7.4.0 through 7.4.2, FortiTester 7.3 all versions, FortiTester 7.2 all versions, FortiTester 7.1 all versions, FortiTester 7.0 all versions, FortiTester 4.2 all versions, FortiVoice 7.0.0 through 7.0.4, FortiVoice 6.4.0 through 6.4.9, FortiVoice 6.0.7 through 6.0.12, FortiWeb 7.6.0, FortiWeb 7.4.0 through 7.4.4, FortiWeb 7.2 all versions, FortiWeb 7.0 all versions, FortiWeb 6.4 all versions allows attacker to disclose sensitive information via specially crafted packets.

Other sources

An Insertion of Sensitive Information Into Sent Data Vulnerability in Fortimanager, FortiMail, FortiNDR, FortOS, FortiPAM, FortiProxy, FortiRecorder, FortiTester, FortiVoice, FortiWeb csfd daemon may allow a remote authenticated attacker to read small and non-arbitrary parts of memory.

FortiGuard

Affected Software

80 affected componentsFixes available
Fortinet FortiManager Cloud>=7.4.1<=7.4.3
Fortinet FortiVoice>=7.0.0<=7.0.4, >=6.4.0<=6.4.9, >=6.0.7<6.0.13
Fortinet FortiMail>=7.4.0<=7.4.2, >=7.2.0<=7.2.6, >=7.0.0<=7.0.9
Fortinet FortiOS>=7.4.0<=7.4.4, >=7.2.0<=7.2.8, >=7.0.0<=7.0.15, >=6.4.0<=6.4.15, >=6.2.0<=6.2.17, >=6.0.0<=6.0.18
Fortinet FortiWeb>=7.4.0<=7.4.4, >=7.2.0<=7.2.11, >=7.0.0<=7.0.11, >=6.4.0<=6.4.3
Fortinet FortiRecorder>=7.2.0<=7.2.1, >=7.0.0<=7.0.4
Fortinet FortiNDR>=7.4.0<=7.4.8, >=7.2.0<=7.2.5, >=7.1.0<=7.1.1, >=7.0.0<=7.0.7, >=1.5.0<=1.5.3
Fortinet FortiPAM>=1.3.0<=1.3.1, >=1.1.0<=1.1.2, >=1.0.0<=1.0.3
Fortinet FortiTester>=7.4.0<=7.4.2, >=7.3.0<=7.3.2, >=7.2.0<=7.2.3, >=7.1.0<=7.1.1, >=4.2.0<=4.2.1
Fortinet FortiProxy>=7.4.0<=7.4.4, >=7.2.0<=7.2.10, >=7.0.0<=7.0.21, >=2.0.0<=2.0.14
Fortinet FortiMail>=7.4.0<=7.4.2
Fortinet FortiMail>=7.2.0<=7.2.6
Fortinet FortiMail>=7.0
Fortinet FortiManager>=7.6.0<=7.6.1
Fortinet FortiManager>=7.4.1<=7.4.3
Fortinet FortiManager Cloud>=7.4.1<=7.4.3
Fortinet FortiNDR>=7.6.0<=7.6.1
Fortinet FortiNDR>=7.4.0<=7.4.8
Fortinet FortiNDR>=7.2
Fortinet FortiNDR>=7.1
Fortinet FortiNDR>=7.0
Fortinet FortiNDR>=1.5
Fortinet FortiOS=.
Fortinet FortiOS>=7.4.0<=7.4.4
Fortinet FortiOS>=7.2.0<=7.2.8
Fortinet FortiOS>=7.0.0<=7.0.15
Fortinet FortiOS>=6.4.0<=6.4.15
Fortinet FortiOS>=6.2
Fortinet FortiOS>=6.0
Fortinet FortiPAM>=1.3
Fortinet FortiPAM>=1.2
Fortinet FortiPAM>=1.1
Fortinet FortiPAM>=1.0
Fortinet FortiProxy>=7.4.0<=7.4.4
Fortinet FortiProxy>=7.2.0<=7.2.10
Fortinet FortiProxy>=7.0
Fortinet FortiProxy>=2.0
Fortinet FortiProxy>=1.2
Fortinet FortiProxy>=1.1
Fortinet FortiProxy>=1.0
Fortinet FortiRecorder>=7.2.0<=7.2.1
Fortinet FortiRecorder>=7.0.0<=7.0.4
Fortinet FortiSASE=4
Fortinet FortiTester>=7.4.0<=7.4.2
Fortinet FortiTester>=7.3
Fortinet FortiTester>=7.2
Fortinet FortiTester>=7.1
Fortinet FortiTester>=7.0
Fortinet FortiTester>=4.2
Fortinet FortiVoice>=7.0.0<=7.0.4
Fortinet FortiVoice>=6.4.0<=6.4.9
Fortinet FortiVoice>=6.0.7<=6.0.12
Fortinet FortiWeb=.
Fortinet FortiWeb>=7.4.0<=7.4.4
Fortinet FortiWeb>=7.2
Fortinet FortiWeb>=7.0
Fortinet FortiWeb>=6.4
Fortinet FortiMail>=7.0.0<7.2.7
Fortinet FortiMail>=7.4.0<7.4.3
Fortinet FortiManager>=7.4.1<7.4.4
Fortinet FortiManager>=7.6.0<7.6.2
Fortinet FortiManager Cloud>=7.4.1<7.4.4
Fortinet FortiNDR>=1.5.0<7.4.9
Fortinet FortiNDR>=7.6.0<=7.6.2
Fortinet FortiOS>=6.0.0<6.4.16
Fortinet FortiOS>=7.0.0<7.0.16
Fortinet FortiOS>=7.2.0<7.2.9
Fortinet FortiOS>=7.4.0<7.4.5
Fortinet FortiOS=7.6.0
Fortinet FortiPAM>=1.0.0<=1.3.1
Fortinet FortiProxy>=1.0.0<7.2.11
Fortinet FortiProxy>=7.4.0<7.4.5
Fortinet FortiRecorder>=7.0.0<7.0.5
Fortinet FortiRecorder>=7.2.0<7.2.2
Fortinet FortiSASE=24.3.20
Fortinet FortiTester>=4.2.0<7.4.3
Fortinet FortiVoice>=6.0.7<6.4.10
Fortinet FortiVoice>=7.0.0<7.0.5
Fortinet FortiWeb>=6.4.0<7.4.5
Fortinet FortiWeb=7.6.0

Remediation

Information

Upgrade to FortiManager Cloud version 7.4.4 or above Upgrade to FortiTester version 7.6.0 or above Upgrade to FortiTester version 7.4.3 or above Upgrade to FortiNDR version 7.6.2 or above Upgrade to FortiNDR version 7.4.9 or above Upgrade to FortiManager version 7.6.2 or above Upgrade to FortiManager version 7.4.4 or above Upgrade to FortiPAM version 1.5.0 or above Upgrade to FortiPAM version 1.4.0 or above Fortinet remediated this issue in FortiSASE version 24.3.b and hence customers do not need to perform any action. Upgrade to FortiOS version 7.6.1 or above Upgrade to FortiOS version 7.4.5 or above Upgrade to FortiOS version 7.2.9 or above Upgrade to FortiOS version 7.0.16 or above Upgrade to FortiOS version 6.4.16 or above Upgrade to FortiRecorder version 7.2.2 or above Upgrade to FortiRecorder version 7.0.5 or above Upgrade to FortiProxy version 7.4.5 or above Upgrade to FortiProxy version 7.2.11 or above Upgrade to FortiMail version 7.6.0 or above Upgrade to FortiMail version 7.4.3 or above Upgrade to FortiMail version 7.2.7 or above Upgrade to FortiWeb version 7.6.1 or above Upgrade to FortiWeb version 7.4.5 or above Upgrade to FortiVoice version 7.2.0 or above Upgrade to FortiVoice version 7.0.5 or above Upgrade to FortiVoice version 6.4.10 or above

Event History

Oct 14, 2025
Advisory Published
via FortiGuard·12:00 AM
Data Sourced
via FortiGuard·12:00 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-47569?

The severity of CVE-2024-47569 is considered high due to the potential exposure of sensitive information.

2

How do I fix CVE-2024-47569?

To fix CVE-2024-47569, update Fortinet products to the latest versions available, specifically versions listed for FortiManager Cloud, FortiVoice, FortiMail, and FortiOS.

3

What products are affected by CVE-2024-47569?

CVE-2024-47569 affects Fortinet FortiManager Cloud, FortiVoice, FortiMail, and FortiOS across various specified versions.

4

What information is potentially exposed due to CVE-2024-47569?

CVE-2024-47569 can lead to the unintended exposure of sensitive information within the data sent by affected Fortinet products.

5

What versions should I upgrade to resolve CVE-2024-47569?

To resolve CVE-2024-47569, users should upgrade to versions 7.4.4 or higher for FortiManager Cloud and FortiVoice, and follow similar upgrade paths for other affected products.

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