FortiManager and FortiAnalyzer
CVE-2024-33504: Use of hard-coded cryptographic key to encrypt sensitive data in FortiManager
A use of hard-coded cryptographic key to encrypt sensitive data vulnerability [CWE-321] in FortiManager 7.6.0 through 7.6.1, 7.4.0 through 7.4.5, 7.2.0 through 7.2.9, 7.0 all versions, 6.4 all versions may allow an attacker with JSON API access permissions to decrypt some secrets even if the 'private-data-encryption' setting is enabled.
Published
Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.
Affected and fixed versions
| Product / branch | Fixed in |
|---|---|
| FortiManager 7.6.0 to 7.6.1 | 7.6.2 or later |
| FortiManager 7.4.0 to 7.4.5 | 7.4.6 or later |
| FortiManager 7.2.0 to 7.2.9 | 7.2.10 or later |
| FortiManager 7.0.0 to 7.0.13 | Upgrade past 7.0.13; see the advisory |
| FortiManager 6.4.0 to 6.4.15 | Upgrade past 6.4.15; see the advisory |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
A use of hard-coded cryptographic key to encrypt sensitive data vulnerability [CWE-321] in FortiManager 7.6.0 through 7.6.1, 7.4.0 through 7.4.5, 7.2.0 through 7.2.9, 7.0 all versions, 6.4 all versions may allow an attacker with JSON API access permissions to decrypt some secrets even if the 'private-data-encryption' setting is enabled.
Sources
KEV status, EPSS score and vendor data refreshed automatically, last on 10 Oct 2026.