dbcve.org
FortimanagerApplication · Fortinet

CVE-2024-40585

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 6.2.12 / 6.4.13 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An insertion of sensitive information into log file vulnerabilities [CWE-532] in FortiManager version 7.4.0, version 7.2.3 and below, version 7.0.8 and below, version 6.4.12 and below, version 6.2.11 and below and FortiAnalyzer version 7.4.0, version 7.2.3 and below, version 7.0.8 and below, version 6.4.12 and below, version 6.2.11 and below eventlog may allow any low privileged user with access to event log section to retrieve certificate private key and encrypted password logged as system log.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FortiManager and FortiAnalyzer versions prior to the fixed releases log sensitive information (certificate private keys and encrypted passwords) into the system event log. Any user with low-privilege access to the event log section can read this sensitive data, resulting in credential and key disclosure.

MitigationApply the vendor-supplied patches/updates to FortiManager and FortiAnalyzer to the fixed versions (7.4.1, 7.2.4, 7.0.9, 6.4.13, 6.2.12 or higher). In the interim, restrict and monitor access to the event log section and audit logs for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortimanagerApplication
Affected:>= 6.2.0, < 7.0.9>= 7.2.0, < 7.2.4= 7.4.0
FortianalyzerApplication
Affected:>= 6.2.0, < 6.2.12>= 6.4.0, < 6.4.13>= 7.0.0, < 7.0.9>= 7.2.0, < 7.2.4= 7.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiManager or FortiAnalyzer version
    Run 'get system status' or 'fnsysctl get system status' from CLI, or check the web UI under Dashboard > Status to view the firmware version
    Affected if Version falls within affected ranges: FortiManager 6.2.0-7.0.8, 7.2.0-7.2.3, or 7.4.0; FortiAnalyzer 6.2.0-6.2.11, 6.4.0-6.4.12, 7.0.0-7.0.8, 7.2.0-7.2.3, or 7.4.0
  2. Review recent event logs for sensitive content
    Navigate to Log View > Event > System in the web UI or run 'execute log filter category 1' followed by 'execute log display' in CLI to review system event logs
    Affected if Logs contain certificate private keys, encrypted passwords, or other credential-like strings in plain text within event log entries
  3. Check for certificate-related log entries
    Filter or search system event logs for keywords such as 'private key', 'certificate', 'pkcs', or look for entries with unusual certificate import/modification events
    Affected if Log entries show private key material or certificate data that should not be recorded in plaintext
  4. Verify event log access permissions
    Check user account privileges in FortiManager/FortiAnalyzer under System > Admin > Administrators to confirm if low-privilege users have access to the event log section
    Affected if Users with read-only or limited privileges can access the event log section where sensitive data may be exposed

Your environment is affected if you run a FortiManager or FortiAnalyzer version listed in the affected ranges AND your event logs contain plaintext private keys or encrypted passwords visible to low-privilege users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.2.12 / 6.4.13 / 7.0.9 or later
Fixed in 6.2.126.4.137.0.9
Interim mitigation

Apply the vendor-supplied patches/updates to FortiManager and FortiAnalyzer to the fixed versions (7.4.1, 7.2.4, 7.0.9, 6.4.13, 6.2.12 or higher). In the interim, restrict and monitor access to the event log section and audit logs for unauthorized access attempts.

Recommended fix High confidence

FortiManager: 7.0.9, 7.2.4, or 7.4.1+ | FortiAnalyzer: 6.2.12, 6.4.13, 7.0.9, 7.2.4, or 7.4.1+

  1. 1. Identify current FortiManager/FortiAnalyzer version via Web UI (System > Settings > System Information) or CLI: get system status
  2. 2. For FortiManager: upgrade to version 7.0.9, 7.2.4, or 7.4.1 or later
  3. 3. For FortiAnalyzer: upgrade to version 6.2.12, 6.4.13, 7.0.9, 7.2.4, or 7.4.1 or later
  4. 4. Download firmware from Fortinet Customer Support portal (https://support.fortinet.com)
  5. 5. Back up current configuration
  6. 6. Upload and install firmware via Web UI (System > Firmware) or CLI: execute firmware upgrade
  7. 7. After upgrade, verify the version and confirm the vulnerability is resolved by checking that sensitive data (private keys, passwords) no longer appears in event logs
  8. 8. Review event log permissions to ensure only authorized administrators have access to event log sections
Caveat Review release notes for version-specific changes; upgrading across major versions (e.g., 6.x to 7.x) may require configuration adjustments and downtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortimanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40585 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data