dbcve.org
FortianalyzerApplication · Fortinet

CVE-2023-44249

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to 7.2.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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 authorization bypass through user-controlled key [CWE-639] vulnerability in Fortinet FortiManager version 7.4.0 and before 7.2.3 and FortiAnalyzer version 7.4.0 and before 7.2.3 allows a remote attacker with low privileges to read sensitive information via 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

FortiManager and FortiAnalyzer versions before 7.2.3 and including 7.4.0 contain an authorization bypass vulnerability (CWE-639) where a low-privileged remote attacker can read sensitive information by manipulating HTTP request parameters to bypass authorization checks.

MitigationUpgrade FortiManager and FortiAnalyzer to version 7.2.3 or later (7.2.x branch) or 7.4.1 or later (7.4.x branch). Apply the latest Fortinet patches for these products.

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.0, <= 6.2.12>= 6.4.0, <= 6.4.13>= 7.0.0, <= 7.0.9>= 7.2.0, < 7.2.4= 7.4.0
FortimanagerApplication
Affected:>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.13>= 7.0.0, <= 7.0.9>= 7.2.0, < 7.2.4= 7.4.0

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
None
Availability
None

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

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 product and version
    Run the CLI command 'get system status' or check the web UI dashboard to view the product name and firmware version. Alternatively, check the /var/log/fortianalyzer/version file or the 'System > Settings' page in the web interface.
    Affected if The product is FortiManager or FortiAnalyzer and the version falls within these ranges: 6.2.0-6.2.12, 6.4.0-6.4.13, 7.0.0-7.0.9, 7.2.0-7.2.3, or 7.4.0.
  2. Verify HTTP management interface is accessible
    Confirm that the web UI or API endpoints are accessible on ports 80/443 or the configured management port. Check via 'get system interface' CLI command to see which interfaces have https or http services enabled.
    Affected if The HTTP/HTTPS management interface is exposed and reachable from the network where attackers could send manipulated requests.
  3. Check for low-privileged user accounts
    Review user accounts in the web UI under 'System > Admin > Administrators' or run 'get admin user' CLI command. Identify accounts with profiles other than 'super_admin' or 'admin' such as 'standard_user' or read-only profiles.
    Affected if Low-privileged non-administrator accounts exist in the system that could exploit this authorization bypass to access sensitive information.

The environment is affected if FortiManager or FortiAnalyzer is running a version within 6.2.0-6.2.12, 6.4.0-6.4.13, 7.0.0-7.0.9, 7.2.0-7.2.3, or 7.4.0, and the management interface is accessible with low-privileged user accounts present.

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

Upgrade FortiManager and FortiAnalyzer to version 7.2.3 or later (7.2.x branch) or 7.4.1 or later (7.4.x branch). Apply the latest Fortinet patches for these products.

Recommended fix High confidence

FortiManager/FortiAnalyzer 7.2.4 or later (or the latest 7.4.x if available); for older branches: 6.2.13+, 6.4.14+, or 7.0.10+

  1. 1. Identify the currently installed FortiManager or FortiAnalyzer version using the web UI (System Settings > Dashboard > Status) or CLI: `get system status`
  2. 2. Based on your current major version, plan the upgrade path: for 6.2.x upgrade to 6.2.13+, for 6.4.x upgrade to 6.4.14+, for 7.0.x upgrade to 7.0.10+, for 7.2.x upgrade to 7.2.4 or later
  3. 3. Download the appropriate firmware from Fortinet Customer Support portal (https://support.fortinet.com)
  4. 4. Back up the current configuration via CLI: `execute backup config tftp <config_name> <tftp_server_ip>` or via web UI
  5. 5. Upload the new firmware via web UI (System Settings > Firmware) or CLI: `execute restore image tftp <image_name> <tftp_server_ip>`
  6. 6. After firmware installation, reboot the device: `execute reboot`
  7. 7. Verify the upgrade was successful and the new version is running: `get system status`
  8. 8. Confirm the vulnerability is resolved by checking the FortiGuard security advisories
Caveat Review Fortinet release notes for any configuration or feature changes between versions; test upgrade 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-2023-44249 — 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-2023-44249 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