dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-50563

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-16
Fix available
A fix is available. Upgrade to 7.4.4 / 7.6.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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 weak authentication in Fortinet FortiManager Cloud, FortiAnalyzer versions 7.6.0 through 7.6.1, 7.4.1 through 7.4.3, FortiAnalyzer Cloud versions 7.4.1 through 7.4.3, FortiManager versions 7.6.0 through 7.6.1, 7.4.1 through 7.4.3, FortiManager Cloud versions 7.4.1 through 7.4.3 allows attacker to execute unauthorized code or commands via a brute-force attack.

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 7.4.1-7.4.3 and 7.6.0-7.6.1 contain a weak authentication mechanism that can be exploited via brute-force attacks, allowing remote attackers to execute unauthorized code or commands without proper credentials.

MitigationApply vendor-supplied patches for affected versions and implement rate limiting/multi-factor authentication on administrative interfaces to mitigate brute-force 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
FortianalyzerApplication
Affected:>= 7.4.1, < 7.4.4>= 7.6.0, < 7.6.2
Fortianalyzer CloudApplication
Affected:>= 7.4.1, < 7.4.4
FortimanagerApplication
Affected:>= 7.4.1, < 7.4.4>= 7.6.0, < 7.6.2
Fortimanager CloudApplication
Affected:>= 7.4.1, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 FortiManager or FortiAnalyzer product type
    Log into the device CLI or web UI and run the command: get system status (CLI) or check System > Settings > About in the web UI to confirm whether the installed product is FortiManager, FortiAnalyzer, FortiManager Cloud, or FortiAnalyzer Cloud
    Affected if The product type is any of these four products listed in the affected products
  2. Determine the installed version number
    In CLI, run: get system status and locate the 'FortiManager version' or 'FortiAnalyzer version' field. In the web UI, go to System > Settings > About to view the firmware version
    Affected if The version displayed matches the affected ranges: 7.4.1 through 7.4.3, or 7.6.0 through 7.6.1
  3. Check if remote management access is enabled
    In CLI, run: show system interface or get system interface to list network interfaces and their IP assignments. Look for interfaces with 'set allowaccess https http ssh' that permit external access
    Affected if The management interface (port1 or others) is accessible from untrusted networks (e.g.,0.0.0.0/0 or internet-facing IPs)
  4. Verify account lockout policy configuration
    In the web UI, go to System Settings > Admin Settings > Security Remediation. In CLI, run: show system lockout-threshold to check if a lockout policy is configured
    Affected if No lockout threshold is set, or the threshold is set too high (e.g., allowing many retry attempts before locking)

You are affected if your FortiManager or FortiAnalyzer (including Cloud variants) is running version 7.4.1 through 7.4.3 or 7.6.0 through 7.6.1 and the management interface is exposed to untrusted networks without adequate account lockout protections.

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.4 / 7.6.2 or later
Fixed in 7.4.47.6.2
Interim mitigation

Apply vendor-supplied patches for affected versions and implement rate limiting/multi-factor authentication on administrative interfaces to mitigate brute-force attempts.

Recommended fix High confidence

FortiManager/FortiAnalyzer 7.4.4 or later; FortiManager/FortiAnalyzer 7.6.2 or later

  1. 1. Identify your current FortiManager or FortiAnalyzer version from the System Settings > Dashboard > System Information widget
  2. 2. Determine the appropriate upgrade path based on your current version branch (7.4.x or 7.6.x)
  3. 3. Download the fixed firmware version from the Fortinet Support Portal (fortinet.com/support)
  4. 4. Back up your current configuration using FortiManager/FortiAnalyzer backup functions
  5. 5. Upload the new firmware image via System Settings > Firmware
  6. 6. Initiate the firmware upgrade and allow the system to reboot
  7. 7. After reboot, verify the new version is installed and confirm all services are operational
  8. 8. Verify the vulnerability is resolved by checking the installed version matches the fixed release
Caveat Standard firmware upgrade precautions apply - ensure configuration backup before upgrading

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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