dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-35273

HIGH · 8.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.4.3 / 7.4.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A out-of-bounds write in Fortinet FortiManager version 7.4.0 through 7.4.2, FortiAnalyzer version 7.4.0 through 7.4.2 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 · moderate confidence

An out-of-bounds write vulnerability in FortiManager and FortiAnalyzer versions 7.4.0 through 7.4.2 allows authenticated attackers to escalate privileges via specially crafted HTTP requests. The vulnerability occurs in the HTTP request handling component where improper bounds checking permits writing data beyond allocated memory boundaries.

MitigationUpgrade FortiManager and FortiAnalyzer to version 7.4.3 or later to address the vulnerability. Alternatively, apply Fortinet's available patches for affected versions.

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:>= 7.4.0, < 7.4.4
Fortianalyzer CloudApplication
Affected:>= 7.4.1, < 7.4.3
FortimanagerApplication
Affected:>= 7.4.0, < 7.4.3
Fortimanager CloudApplication
Affected:>= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Fortinet product in use
    Access the FortiManager or FortiAnalyzer CLI or web interface and determine the exact product name (FortiManager, FortiManager Cloud, FortiAnalyzer, or FortiAnalyzer Cloud)
    Affected if The product is one of the four affected products listed in the CVE
  2. Determine the installed firmware version
    Run the command 'get system status' in the CLI or check the version displayed in the web interface System > Dashboard > Status page
    Affected if The version falls within any of these ranges: FortiAnalyzer >= 7.4.0 and < 7.4.4; FortiAnalyzer Cloud >= 7.4.1 and < 7.4.3; FortiManager >= 7.4.0 and < 7.4.3; FortiManager Cloud >= 7.4.1 and < 7.4.3
  3. Verify HTTP management interface is accessible
    Attempt to reach the management web interface via HTTP or HTTPS on the configured management port (default 443 for HTTPS). Check System > Network > Interface settings in the web UI to confirm which interfaces have HTTPS management enabled
    Affected if The HTTP/HTTPS management interface is exposed and accessible from a network where attackers could send requests
  4. Confirm user authentication is configured
    Check the admin user list under System > Administrators in the web UI or run 'get system admin' in the CLI. Verify that local or remote authentication is enabled for administrative access
    Affected if Administrative or limited user accounts exist in the system that could be leveraged for authentication by an attacker

You are affected if your FortiManager or FortiAnalyzer (or Cloud variants) is running version 7.4.0 through the version just before the fixed release, has the web-based management interface exposed, and has user accounts configured for authentication.

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.4.3 / 7.4.4 or later
Fixed in 7.4.37.4.4
Interim mitigation

Upgrade FortiManager and FortiAnalyzer to version 7.4.3 or later to address the vulnerability. Alternatively, apply Fortinet's available patches for affected versions.

Recommended fix High confidence

FortiManager >= 7.4.3; FortiAnalyzer >= 7.4.4 (on-premise) or >= 7.4.3 (Cloud); FortiManager Cloud >= 7.4.3

  1. 1. Identify the specific Fortinet product in use (FortiManager, FortiAnalyzer, or their Cloud variants)
  2. 2. Back up current configuration according to Fortinet best practices
  3. 3. Download the appropriate fixed firmware version from Fortinet support portal
  4. 4. Upload the firmware to the device via web UI or CLI
  5. 5. Verify the upgrade completed successfully and the device is operational
  6. 6. Confirm the version number matches or exceeds the fixed release
Caveat Review Fortinet release notes for 7.4.3/7.4.4 for any configuration or feature changes before upgrading

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 / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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