dbcve.org
FortisiemApplication · Fortinet

CVE-2023-36551

MEDIUM · 5.3 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to 6.7.6 or later.
See remediation →
62/100
Remediation priority · Elevated
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 exposure of sensitive information to an unauthorized actor in Fortinet FortiSIEM version 6.7.0 through 6.7.5 allows attacker to information disclosure 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 · moderate confidence

FortiSIEM versions 6.7.0 through 6.7.5 contain an information disclosure vulnerability where a crafted HTTP request allows an unauthenticated attacker to access sensitive information. The attack is network-based and exploits the lack of proper authorization controls on certain HTTP endpoints.

MitigationUpgrade FortiSIEM to version 6.7.6 or later per Fortinet's release notes. If immediate patching is not possible, restrict network access to FortiSIEM management interfaces to trusted IP addresses using firewall rules or access control lists.

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
FortisiemApplication
Affected:>= 6.7.0, < 6.7.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 the FortiSIEM version
    Access the FortiSIEM web UI or CLI and navigate to Admin > Settings > About, or run 'ph статус' in the CLI to retrieve the installed version number.
    Affected if The installed version is 6.7.0, 6.7.1, 6.7.2, 6.7.3, 6.7.4, or 6.7.5.
  2. Verify HTTP management interface exposure
    Determine if the FortiSIEM web interface (port 443 by default) is reachable from untrusted networks by reviewing firewall rules, ACLs, or performing a network connectivity test from an external host.
    Affected if The FortiSIEM HTTP/HTTPS management port is accessible from networks that are not explicitly trusted.
  3. Review HTTP access logs for unauthorized requests
    Examine FortiSIEM event logs or web server logs for unusual HTTP GET requests from unauthenticated sources that may indicate probing for sensitive endpoints.
    Affected if Logs show HTTP requests from unauthenticated IP addresses to arbitrary endpoints that return sensitive information.

You are affected if FortiSIEM version is between 6.7.0 and 6.7.5 inclusive and the management interface is network-accessible to untrusted parties.

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 6.7.6 or later
Fixed in 6.7.6
Interim mitigation

Upgrade FortiSIEM to version 6.7.6 or later per Fortinet's release notes. If immediate patching is not possible, restrict network access to FortiSIEM management interfaces to trusted IP addresses using firewall rules or access control lists.

Recommended fix High confidence

FortiSIEM 6.7.6 or later

  1. 1. Review Fortinet FortiSIEM upgrade documentation and release notes for version 6.7.6
  2. 2. Create a complete backup of the current FortiSIEM configuration and database
  3. 3. Schedule a maintenance window as upgrades may require system downtime
  4. 4. Download FortiSIEM version 6.7.6 or later from Fortinet support portal
  5. 5. Follow Fortinet's official upgrade procedure for FortiSIEM 6.7.x series
  6. 6. After upgrade, verify the system is functioning normally
  7. 7. Validate that the CVE-2023-36551 vulnerability is no longer present
Caveat Review release notes for any configuration or feature changes between 6.7.0-6.7.5 and 6.7.6; test in staging environment before production deployment

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

Fix this in Fortisiem 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 the upgrade done

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-2023-36551 — 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-36551 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