dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-33502

HIGH · 7.2 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.2.6 / 7.4.3 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 versions 7.4.0 through 7.4.2 and 7.2.0 through 7.2.5 and 7.0.0 through 7.0.12 and 6.4.0 through 6.4.14 and 6.2.0 through 6.2.12 and 6.0.0 through 6.0.12 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 FortiManager and FortiAnalyzer allows remote attackers to access restricted directories and potentially execute unauthorized code or commands via specially crafted HTTP/HTTPS requests containing directory traversal sequences.

MitigationApply Fortinet's security patches to upgrade to a supported version (7.4.3+, 7.2.6+, 7.0.13+, 6.4.15+, 6.2.13+, 6.0.13+) as specified in the Fortinet advisory, and restrict management interface access to trusted networks.

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.0.0, < 7.2.6>= 7.4.0, < 7.4.3
FortimanagerApplication
Affected:>= 6.0.0, < 7.2.6>= 7.4.0, < 7.4.3

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 product and version
    Run the command 'get system status' via CLI or check the web UI dashboard to determine if the installed product is FortiManager or FortiAnalyzer and note the exact firmware version number
    Affected if The version falls within 6.0.0 to 7.2.5, or 7.4.0 to 7.4.2
  2. Confirm management interface exposure
    Check network configuration to determine if the FortiManager/FortiAnalyzer web UI (HTTP/HTTPS on ports 80/443 or custom management ports) is accessible from untrusted networks
    Affected if The management interface is reachable from the internet or untrusted networks
  3. Review web server logs for traversal patterns
    Examine HTTP access logs in /var/log/ or via the FortiView/logs interface for requests containing '../' sequences, such as 'GET /..' or '..\' patterns directed at the web interface
    Affected if Suspicious directory traversal sequences are found in web access logs
  4. Check for unauthorized file access indicators
    Review system event logs and file integrity monitoring for any unexpected access to restricted directories such as /etc, /var, or configuration repositories
    Affected if Logs show access to system directories that would not result from normal administrative operations

You are affected if your FortiManager or FortiAnalyzer runs a version between 6.0.0 and 7.2.5 or between 7.4.0 and 7.4.2 and the management interface is network-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.2.6 / 7.4.3 or later
Fixed in 7.2.67.4.3
Interim mitigation

Apply Fortinet's security patches to upgrade to a supported version (7.4.3+, 7.2.6+, 7.0.13+, 6.4.15+, 6.2.13+, 6.0.13+) as specified in the Fortinet advisory, and restrict management interface access to trusted networks.

Recommended fix High confidence

Upgrade to FortiManager/FortiAnalyzer 7.2.6 or 7.4.3 (or later stable release)

  1. Identify the current FortiManager or FortiAnalyzer version using the web UI or CLI (get system status)
  2. Determine which major version branch you are on (6.x, 7.0.x, 7.2.x, or 7.4.x)
  3. Backup the current configuration using 'execute backup full-config' via CLI or via web UI
  4. For FortiManager: If on 7.4.x branch, upgrade to version 7.4.3 or later. If on 7.2.x or earlier, upgrade to 7.2.6 or later
  5. For FortiAnalyzer: If on 7.4.x branch, upgrade to version 7.4.3 or later. If on 7.2.x or earlier, upgrade to 7.2.6 or later
  6. Download the firmware from Fortinet Customer Support portal and upload via FortiManager/FortiAnalyzer web UI (System > Firmware) or CLI (execute system firmware upgrade)
  7. After reboot, verify the upgrade was successful and the version is >= 7.2.6 or >= 7.4.3
  8. Verify the vulnerability is resolved by confirming the version and reviewing release notes
Caveat Review Fortinet release notes for 7.2.6/7.4.3 for any configuration or feature changes that may affect your deployment; always test in a non-production environment first

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-33502 — 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-33502 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