dbcve.org
FortianalyzerApplication · Fortinet

CVE-2023-44253

MEDIUM · 5.0 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to after 7.2.3 or later.
See remediation →
56/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 exposure of sensitive information to an unauthorized actor vulnerability [CWE-200] in Fortinet FortiManager version 7.4.0 through 7.4.1 and before 7.2.5, FortiAnalyzer version 7.4.0 through 7.4.1 and before 7.2.5 and FortiAnalyzer-BigData before 7.2.5 allows an adom administrator to enumerate other adoms and device names via crafted HTTP or HTTPS 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

This is an information disclosure vulnerability in FortiManager and FortiAnalyzer where an authenticated adom administrator (a lower-privileged administrative domain user) can enumerate other ADOMs and device names by sending crafted HTTP/HTTPS requests. The vulnerability exposes sensitive infrastructure topology information (ADOM names and managed device identities) to unauthorized parties within the same system.

MitigationUpgrade FortiManager and FortiAnalyzer to version 7.2.5 or later, or version 7.4.2 or later. Restrict adom administrator privileges where possible and monitor for anomalous API/HTTP request patterns.

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.14>= 7.0.0, <= 7.0.11>= 7.2.0, <= 7.2.3= 7.4.0= 7.4.1
FortimanagerApplication
Affected:>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.14>= 7.0.0, <= 7.0.11>= 7.2.0, <= 7.2.3= 7.4.0= 7.4.1

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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 product and version
    Access the FortiManager or FortiAnalyzer web UI, go to System > Settings > About, or run 'get system status' via CLI to retrieve the exact version number
    Affected if The installed version falls within any of these ranges: 6.2.0 to 6.2.12, 6.4.0 to 6.4.14, 7.0.0 to 7.0.11, 7.2.0 to 7.2.3, 7.4.0, or 7.4.1
  2. Confirm ADOM feature is enabled
    In the web UI, navigate to Global > System > Settings, or run 'get system admin setting' via CLI and check if 'adom mode' is set to something other than 'normal'
    Affected if ADOM mode is enabled (specific or normal) and the version is in the affected list
  3. Check for adom administrator accounts
    In the web UI, go to Local Users & Groups > Administrators, or run 'get system admin' via CLI, and identify accounts with 'adom admin' profile type
    Affected if Any adom administrator accounts exist in the system
  4. Review access logs for anomalous API patterns
    In the web UI, go to Log & Report > Event Log > System Events, filter for admin login and API activity, looking for repeated GET requests to '/api/v2/monitor/' endpoints from lower-privileged users
    Affected if Multiple API requests targeting other ADOMs or device information are observed from adom administrator sessions

A user is affected if they run a vulnerable FortiManager or FortiAnalyzer version within the affected ranges and have adom administrator accounts configured on the system.

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 a release after 7.2.3
Interim mitigation

Upgrade FortiManager and FortiAnalyzer to version 7.2.5 or later, or version 7.4.2 or later. Restrict adom administrator privileges where possible and monitor for anomalous API/HTTP request patterns.

Recommended fix High confidence

FortiManager/FortiAnalyzer 7.2.5 or later, or 7.4.2 or later; FortiAnalyzer-BigData 7.2.5 or later

  1. 1. Identify the FortiManager and FortiAnalyzer versions currently deployed in your environment
  2. 2. For FortiManager: upgrade to version 7.2.5 or later, or 7.4.2 or later
  3. 3. For FortiAnalyzer: upgrade to version 7.2.5 or later, or 7.4.2 or later
  4. 4. For FortiAnalyzer-BigData: upgrade to version 7.2.5 or later
  5. 5. After upgrade, verify the adom administrator role permissions are correctly configured and test that enumeration is no longer possible
  6. 6. Review audit logs to confirm no unauthorized enumeration occurred prior to patching
Caveat Review release notes for any configuration or feature changes between versions 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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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