dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-33505

HIGH · 7.3 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 7.2.6 / 7.2.7 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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
A heap-based buffer overflow in Fortinet FortiAnalyzer version 7.4.0 through 7.4.2, 7.2.0 through 7.2.5, 7.0.0 through 7.0.12, 6.4.0 through 6.4.14, FortiManager version 7.4.0 through 7.4.2, 7.2.0 through 7.2.5, 7.0.0 through 7.0.12, 6.4.0 through 6.4.14 allows attacker to escalation of privilege via specially crafted http 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

Heap-based buffer overflow vulnerability in FortiAnalyzer and FortiManager allows authenticated attackers to escalate privileges via specially crafted HTTP requests. The flaw affects multiple version ranges across both product lines.

MitigationApply Fortinet's patches for affected versions; upgrade to fixed releases (7.4.3+, 7.2.6+, 7.0.13+, 6.4.15+) or later supported versions. Restrict administrative 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.4.0, < 7.2.6>= 7.4.0, < 7.4.3
FortimanagerApplication
Affected:>= 6.0.0, < 7.2.7>= 7.4.0, < 7.4.3
Fortimanager CloudApplication
Affected:>= 6.4.1, < 7.2.7>= 7.4.1, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Fortinet product
    Log into the Fortinet device CLI and run 'get system status' or check the web UI dashboard to confirm the product name (FortiAnalyzer, FortiManager, or FortiManager Cloud)
    Affected if The product is FortiAnalyzer, FortiManager, or FortiManager Cloud
  2. Check the installed firmware version
    Run 'get system status' in the CLI or view the version in the web UI under Dashboard > Status. Note the exact version number (e.g., 7.4.0, 7.2.5)
    Affected if The version falls within: FortiAnalyzer >= 6.4.0 and < 7.2.6, or >= 7.4.0 and < 7.4.3; FortiManager >= 6.0.0 and < 7.2.7, or >= 7.4.0 and < 7.4.3; FortiManager Cloud >= 6.4.1 and < 7.2.7, or >= 7.4.1 and < 7.4.3
  3. Verify administrative access exposure
    Check the network configuration for the administrative interface (GUI/CLI) by running 'get system interface' and reviewing firewall policies. Determine if the HTTPS/HTTP admin port is accessible from untrusted networks
    Affected if The administrative interface (port 443 or 80) is exposed to the internet or untrusted networks without VPN or IP restrictions
  4. Review logs for suspicious HTTP requests
    Check FortiAnalyzer/FortiManager logs under Log & Report > Event Logs > System Events for abnormal or specially crafted HTTP requests, especially those associated with privilege escalation or unusual administrative actions
    Affected if Unexplained HTTP requests appear in logs, especially from authenticated users performing unexpected privilege escalation actions

You are affected if you are running any FortiAnalyzer, FortiManager, or FortiManager Cloud version within the affected ranges AND the administrative interface is accessible to authenticated attackers.

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.2.7 / 7.4.3 or later
Fixed in 7.2.67.2.77.4.3
Interim mitigation

Apply Fortinet's patches for affected versions; upgrade to fixed releases (7.4.3+, 7.2.6+, 7.0.13+, 6.4.15+) or later supported versions. Restrict administrative access to trusted networks.

Recommended fix High confidence

FortiAnalyzer: upgrade to 7.2.6 or 7.4.3; FortiManager: upgrade to 7.2.7 or 7.4.3; FortiManager Cloud: upgrade to 7.2.7 or 7.4.3

  1. 1. Identify the current FortiAnalyzer/FortiManager version via Web UI (System Settings > Dashboard > Status) or CLI: 'get system status'
  2. 2. Determine the appropriate upgrade target based on current version branch: if running 6.4.x or 7.0.x, upgrade to 7.2.6; if running 7.2.x, upgrade to 7.2.6; if running 7.4.x, upgrade to 7.4.3
  3. 3. Download the firmware upgrade from Fortinet Customer Support portal (https://support.fortinet.com)
  4. 4. Backup the current configuration via Web UI (System Settings > Maintenance > Backup & Restore) or CLI: 'execute backup full-config'
  5. 5. Upload the firmware image via Web UI (System Settings > Firmware) or CLI: 'execute system firmware-upgrade <image-file> tftp/ftp/USB
  6. 6. Reboot the device after upgrade completes
  7. 7. Verify the upgrade was successful and the version matches the target via 'get system status'
Caveat Review Fortinet release notes for the target version for any configuration or feature changes; major version upgrades (e.g., 6.4.x to 7.x) may require compatibility checks with managed devices

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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