dbcve.org
FortiaiopsApplication · Fortinet

CVE-2024-27784

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple Exposure of sensitive information to an unauthorized actor weaknesses [CWE-200] vulnerability in Fortinet FortiAIOps 2.0.0 may allow an authenticated, remote attacker to retrieve sensitive information from the API endpoint or log files.

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

FortiAIOps 2.0.0 contains an information disclosure vulnerability (CWE-200) where an authenticated attacker can retrieve sensitive information from API endpoints or log files. The attacker requires valid authentication credentials but can exploit improper access controls to access data they should not see.

MitigationApply the Fortinet patch or upgrade to a version beyond FortiAIOps 2.0.0 that addresses this vulnerability. Review API access controls and audit log files for any evidence of unauthorized access.

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
FortiaiopsApplication
Affected:= 2.0.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 FortiAIOps version
    Check the installed FortiAIOps version using the Fortinet CLI command 'get system status' or through the web UI under System > Settings > About. Alternatively, check the /var/log/fortiaiop/logs directory for version indicators.
    Affected if The installed version is exactly 2.0.0. Versions beyond 2.0.0 are not affected.
  2. Review API access controls
    Examine the FortiAIOps API configuration and user role permissions. Use the CLI command 'show system api-user' or check API access policies in the web UI under API Users or IAM settings to verify which users have access to which API endpoints.
    Affected if API users with limited roles can access endpoints or retrieve data outside their authorized scope, indicating improper access controls.
  3. Audit log file access
    Review FortiAIOps log files in the standard log directory (typically /var/log/fortiaiop or through the log viewer in the web UI). Look for API queries or file access from user accounts that should not have permission to view certain data.
    Affected if Logs show API requests or log file access from authenticated users retrieving information they should not be authorized to see.
  4. Check for unauthorized data retrieval patterns
    Analyze API access logs for unusual data retrieval patterns, such as users accessing data outside their department, role, or tenant. Cross-reference API request logs with expected user permissions.
    Affected if Authenticated users successfully accessed sensitive information from API endpoints or log files that should be restricted based on their role.

You are affected if FortiAIOps is exactly version 2.0.0 AND evidence exists of unauthorized access to API endpoints or log files by users with limited permissions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Fortinet patch or upgrade to a version beyond FortiAIOps 2.0.0 that addresses this vulnerability. Review API access controls and audit log files for any evidence of unauthorized access.

Fix this in Fortiaiops Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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