dbcve.org
FortianalyzerApplication · Fortinet

CVE-2023-44254

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 7.2.5 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 FortiAnalyzer version 7.4.1 and before 7.2.5 and FortiManager version 7.4.1 and before 7.2.5 may allow a remote attacker with low privileges to read sensitive data via a crafted HTTP request.

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 CWE-639 authorization bypass vulnerability in FortiAnalyzer and FortiManager versions before 7.2.5 and 7.4.1 allows remote attackers with low-privilege accounts to read sensitive data by manipulating user-controlled keys in crafted HTTP requests. The vulnerability stems from improper authorization checks on certain API endpoints or parameters.

MitigationApply Fortinet's security patches: upgrade to FortiAnalyzer/FortiManager 7.2.5 or later, or 7.4.2 or later. No configuration workarounds are available; patching is the only remediation.

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, < 7.2.5= 7.4.0
FortimanagerApplication
Affected:>= 6.2.0, < 7.2.5= 7.4.0
Fortianalyzer Big DataApplication
Affected:>= 7.2.0, <= 7.2.5

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
    Determine whether the system is running FortiAnalyzer, FortiManager, or FortiAnalyzer Big Data. This can be done via the web UI footer, CLI command 'get system status', or API endpoint that returns product information.
    Affected if The product is FortiAnalyzer, FortiManager, or FortiAnalyzer Big Data.
  2. Check the installed version number
    Retrieve the firmware version via the web UI (System Settings > Dashboard > System Information widget), CLI command 'get system status', or API call. Compare the version to the affected ranges: FortiAnalyzer/FortiManager versions 6.2.0 through 7.2.4, or version 7.4.0; FortiAnalyzer Big Data versions 7.2.0 through 7.2.5.
    Affected if The installed version falls within 6.2.0 to 7.2.4, equals 7.4.0, or for Big Data equals 7.2.0 through 7.2.5.
  3. Verify API access is enabled
    Check if the REST API is accessible by attempting a query to the API endpoints (typically port 443 or 8443). In the web UI, go to System Settings > Administrators > REST API Admins to see if any API users exist. In CLI, use 'get system api-user' to list configured API users.
    Affected if REST API access is enabled and low-privilege API users or administrator accounts exist.
  4. Identify low-privilege accounts
    Review user accounts with limited privileges. In CLI, use 'get system admin' or 'get system api-user' to list accounts. In the web UI, check System Settings > Administrators. Look for accounts with read-only or restricted access profiles.
    Affected if Low-privilege user accounts or API users are configured on the system.
  5. Confirm the system is exposed to network
    Verify whether the management interface or API is accessible from untrusted networks. Check firewall rules, interface bindings, and whether the web UI/API is bound to WAN-facing interfaces using 'get system interface' or reviewing network configuration.
    Affected if The API or management interface is reachable from external or untrusted networks.

A system is affected if it runs FortiAnalyzer, FortiManager, or FortiAnalyzer Big Data with a version in the vulnerable range AND has API access enabled with low-privilege 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.5 or later
Fixed in 7.2.5
Interim mitigation

Apply Fortinet's security patches: upgrade to FortiAnalyzer/FortiManager 7.2.5 or later, or 7.4.2 or later. No configuration workarounds are available; patching is the only remediation.

Recommended fix High confidence

FortiAnalyzer/FortiManager 7.2.6 or 7.4.1 and later; FortiAnalyzer Big Data 7.2.6 or later

  1. 1. Identify the current FortiAnalyzer/FortiManager version by navigating to System Settings > FortiGuard or using the 'get system status' CLI command
  2. 2. If running version 6.2.0 through 7.2.4, upgrade to version 7.2.5 or later (7.2.6 recommended)
  3. 3. If running version 7.4.0, upgrade to version 7.4.1 or later
  4. 4. For FortiAnalyzer Big Data: upgrade to version 7.2.6 or later
  5. 5. After upgrade, verify the system status confirms the new version is running
  6. 6. Test that the authorization controls now properly enforce access restrictions for low-privilege users
Caveat Standard upgrade precautions apply - review release notes for breaking changes, backup configuration before upgrading, and schedule maintenance window

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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