dbcve.org
FortianalyzerApplication · Fortinet

CVE-2021-32603

MEDIUM · 6.5 CVSS v3.1 Published 2021-08-05
Fix available
A fix is available. Upgrade to 6.2.8 / 6.4.6 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
A server-side request forgery (SSRF) (CWE-918) vulnerability in FortiManager and FortiAnalyser GUI 7.0.0, 6.4.5 and below, 6.2.7 and below, 6.0.11 and below, 5.6.11 and below may allow a remote and authenticated attacker to access unauthorized files and services on the system via specifically crafted web 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

A server-side request forgery (SSRF) vulnerability exists in FortiManager and FortiAnalyser GUI across multiple versions (7.0.0, 6.4.5 and below, 6.2.7 and below, 6.0.11 and below, 5.6.11 and below). An authenticated remote attacker can exploit this by sending specifically crafted web requests to the GUI interface, causing the server to make unintended requests to internal resources, potentially exposing unauthorized files and services.

MitigationApply the vendor-supplied patches by upgrading FortiManager and FortiAnalyser to the fixed versions (7.0.1 or later, 6.4.6 or later, 6.2.8 or later, 6.0.12 or later, 5.6.12 or later). If immediate patching is not possible, restrict GUI access to trusted networks or IP ranges using access policies.

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:>= 5.6.0, < 6.2.8>= 6.4.0, < 6.4.6>= 7.0.0, < 7.0.1
FortimanagerApplication
Affected:>= 5.6.0, < 6.2.8>= 6.4.0, < 6.4.6>= 7.0.0, < 7.0.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
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 Fortinet product
    Run 'get system status' or 'fnsysctl grep "FortiManager\|FortiAnalyzer" /etc/version' via CLI to confirm the product name
    Affected if Product is FortiManager or FortiAnalyser
  2. Determine the installed version
    Run 'get system status' or 'fnsysctl cat /etc/version' via CLI to retrieve the firmware version number
    Affected if Version is 5.6.0 to 5.6.11, 6.0.0 to 6.0.11, 6.2.0 to 6.2.7, 6.4.0 to 6.4.5, or 7.0.0
  3. Confirm GUI interface is accessible
    Check network configuration via 'get system interface' or review access policies to determine if HTTP/HTTPS GUI access is enabled on external or untrusted interfaces
    Affected if GUI is exposed to untrusted networks (not limited to trusted IPs)
  4. Verify admin user access
    Review admin account configuration with 'get admin user' to identify if weak or default credentials exist, or if excessive privileges are assigned to non-administrator accounts
    Affected if Untrusted or compromised admin accounts exist with GUI access

You are affected if you run FortiManager or FortiAnalyser with GUI enabled and your version falls within 5.6.0-5.6.11, 6.0.0-6.0.11, 6.2.0-6.2.7, 6.4.0-6.4.5, or 7.0.0.

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
Upgrade available Upgrade to 6.2.8 / 6.4.6 / 7.0.1 or later
Fixed in 6.2.86.4.67.0.1
Interim mitigation

Apply the vendor-supplied patches by upgrading FortiManager and FortiAnalyser to the fixed versions (7.0.1 or later, 6.4.6 or later, 6.2.8 or later, 6.0.12 or later, 5.6.12 or later). If immediate patching is not possible, restrict GUI access to trusted networks or IP ranges using access policies.

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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