dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-36512

HIGH · 7.2 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.0.13 / 7.2.6 or later.
See remediation →
78/100
Remediation priority · High
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 improper limitation of a pathname to a restricted directory ('path traversal') in Fortinet FortiManager, FortiAnalyzer 7.4.0 through 7.4.3 and 7.2.0 through 7.2.5 and 7.0.2 through 7.0.12 and 6.2.10 through 6.2.13 allows attacker to execute unauthorized code or commands via crafted HTTP or HTTPS requests.

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

A path traversal vulnerability in Fortinet FortiManager and FortiAnalyzer allows attackers to escape restricted directories and execute unauthorized code or commands via crafted HTTP or HTTPS requests. The vulnerability stems from improper limitation of pathnames, enabling directory traversal attacks.

MitigationApply the vendor-supplied firmware patches for the affected versions (7.4.4, 7.2.6, 7.0.13, 6.2.14 or later). If immediate patching is not possible, restrict administrative access to trusted IP addresses and disable unused management interfaces.

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
FortianalyzerApplication
Affected:>= 6.2.10, < 7.0.13>= 7.2.0, < 7.2.6>= 7.4.0, < 7.4.4
FortimanagerApplication
Affected:>= 6.2.10, < 7.0.13>= 7.2.0, < 7.2.6>= 7.4.0, < 7.4.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the installed FortiManager or FortiAnalyzer version
    Run 'get system status' in the CLI or check the web UI login page footer for the version number. Compare the installed version against the affected ranges: 6.2.10 to <7.0.13, 7.2.0 to <7.2.6, or 7.4.0 to <7.4.4
    Affected if The installed version falls within any of the affected version ranges
  2. Confirm the HTTP/HTTPS management interface is enabled
    Check the system settings via CLI with 'get system interface' or inspect the web interface accessibility on ports 80/443 or 8080/8443. The vulnerability is exploitable only if the web-based management interface is active
    Affected if The management web interface is enabled and reachable
  3. Determine if the management interface is exposed to untrusted networks
    Review firewall rules or access lists that control which IP addresses can reach the management interface ports. Check if the interface is bound to WAN-facing IPs or has permit rules from any-source address
    Affected if The management interface is accessible from untrusted networks or the internet
  4. Review admin accounts and system logs for indicators of compromise
    Check for unauthorized administrator accounts using 'get system admin' in CLI. Review system event logs for unusual file access patterns, failed authentication spikes, or commands involving '../' path sequences
    Affected if Unexpected admin accounts exist or logs show path traversal patterns

You are affected if your FortiManager or FortiAnalyzer runs a version within 6.2.10 to <7.0.13, 7.2.0 to <7.2.6, or 7.4.0 to <7.4.4 AND the HTTP/HTTPS management interface is enabled and accessible.

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 7.0.13 / 7.2.6 / 7.4.4 or later
Fixed in 7.0.137.2.67.4.4
Interim mitigation

Apply the vendor-supplied firmware patches for the affected versions (7.4.4, 7.2.6, 7.0.13, 6.2.14 or later). If immediate patching is not possible, restrict administrative access to trusted IP addresses and disable unused management interfaces.

Recommended fix High confidence

FortiManager/FortiAnalyzer 7.4.4 or later; 7.2.6 or later; 7.0.13 or later

  1. Identify your current FortiManager or FortiAnalyzer version using the web GUI or CLI command 'get system status'
  2. Download the appropriate fixed version from Fortinet support portal: 7.4.4 or later, 7.2.6 or later, or 7.0.13 or later
  3. Plan upgrade during maintenance window following Fortinet upgrade best practices
  4. Backup current configuration using 'execute backup full-config'
  5. Upload and install the firmware upgrade via web GUI (System > Firmware) or CLI (execute system firmware upgrade)
  6. After upgrade, verify version using 'get system status' and confirm the path traversal vulnerability is resolved
  7. Test critical functionality to ensure normal operations
Caveat Review Fortinet release notes for your specific upgrade path for any configuration or feature changes between versions

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36512 — 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-36512 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