dbcve.org
FortiadcApplication · Fortinet

CVE-2021-32591

MEDIUM · 5.3 CVSS v3.1 Published 2021-12-08
Fix available
A fix is available. Upgrade to after 6.4.5 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 missing cryptographic steps vulnerability in the function that encrypts users' LDAP and RADIUS credentials in FortiSandbox before 4.0.1, FortiWeb before 6.3.12, FortiADC before 6.2.1, FortiMail 7.0.1 and earlier may allow an attacker in possession of the password store to compromise the confidentiality of the encrypted secrets.

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

A detailed technical summary for this CVE is being prepared.

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
FortiadcApplication
Affected:>= 5.0.0, <= 5.4.4>= 6.0.0, <= 6.0.3>= 6.1.0, <= 6.1.3= 6.2.0= 6.2.1
FortimailApplication
Affected:all versions>= 5.0, <= 5.6.3>= 6.0.0, <= 6.0.11>= 6.2.0, <= 6.2.7>= 6.4.0, <= 6.4.5= 7.0.0= 7.0.1
FortisandboxApplication
Affected:>= 3.2.0, <= 3.2.2= 4.0.0
FortiwebApplication
Affected:>= 5.7.0, <= 5.7.3>= 5.8.0, <= 5.8.7>= 6.0.0, <= 6.0.7>= 6.1.0, <= 6.1.2>= 6.2.0, <= 6.2.4>= 6.3.0, <= 6.3.11= 5.9.0= 5.9.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

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 6.4.5
Vendor patch fortiguard.com →
Recommended fix High confidence

FortiADC: 6.2.1+ | FortiMail: 7.0.2+ | FortiSandbox: 4.0.1+ | FortiWeb: 6.3.12+

  1. 1. Identify the Fortinet product (FortiADC, FortiMail, FortiSandbox, or FortiWeb) from the affected list in your environment
  2. 2. Determine the current installed version of the affected product
  3. 3. For FortiADC: upgrade to version 6.2.1 or later (6.2.0 is affected, 6.2.1 contains the fix)
  4. 4. For FortiMail: upgrade to version 7.0.2 or later (versions 7.0.1 and earlier are affected)
  5. 5. For FortiSandbox: upgrade to version 4.0.1 or later (versions 3.2.0-3.2.2 and 4.0.0 are affected)
  6. 6. For FortiWeb: upgrade to version 6.3.12 or later (versions 5.7.0-5.7.3, 5.8.0-5.8.7, 6.0.0-6.0.7, and 6.1.0-6.1.2 are affected)
  7. 7. After upgrade, verify the LDAP and RADIUS credential encryption functionality works correctly
  8. 8. Review audit logs for any signs of unauthorized access to the password store
Caveat Standard Fortinet upgrade considerations apply - review release notes for your specific version for any configuration or compatibility changes

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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