dbcve.org
FortimailApplication · Fortinet

CVE-2020-9294

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-27
Fix available
A fix is available. Upgrade to after 6.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
An improper authentication vulnerability in FortiMail 5.4.10, 6.0.7, 6.2.2 and earlier and FortiVoiceEntreprise 6.0.0 and 6.0.1 may allow a remote unauthenticated attacker to access the system as a legitimate user by requesting a password change via the user interface.

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 improper authentication vulnerability in FortiMail and FortiVoiceEnterprise web interfaces that allows remote unauthenticated attackers to reset legitimate user passwords by directly requesting a password change through the UI, bypassing proper authentication controls.

MitigationUpgrade FortiMail to version 6.0.8, 6.2.3, 6.4.0 or later and FortiVoiceEnterprise to version 6.0.2 or later. Apply network segmentation to restrict management interface access from untrusted networks as an interim control.

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
FortimailApplication
Affected:<= 5.4.10>= 6.0.0, <= 6.0.7>= 6.2.0, <= 6.2.2
FortivoiceApplication
Affected:>= 6.0.0, <= 6.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 FortiMail version
    Log into the FortiMail web UI and navigate to Dashboard > Status, or run CLI command 'get system status' to retrieve the firmware version.
    Affected if The version is 5.4.10 or below, between 6.0.0 and 6.0.7 inclusive, or between 6.2.0 and 6.2.2 inclusive.
  2. Identify FortiVoice version
    Log into the FortiVoice web UI and navigate to Dashboard > System Information, or run CLI command 'get system status' to retrieve the firmware version.
    Affected if The version is between 6.0.0 and 6.0.1 inclusive.
  3. Verify web management interface is enabled
    Check the interface configuration via CLI using 'get system interface' or via web UI under Network > Interfaces. Look for 'https' or 'http' in the service access settings for the management interface.
    Affected if HTTP or HTTPS management access is enabled on the interface.
  4. Check management interface network exposure
    Review firewall policies and interface settings to determine if the management interface (usually port1) is reachable from untrusted networks or the internet. Use 'diagnose ip address list' to see interface IPs and review access list configurations.
    Affected if The management interface IP is accessible from untrusted or external networks without proper network segmentation.

You are affected if you run a vulnerable FortiMail or FortiVoice version AND the web management interface is exposed to untrusted networks, allowing unauthenticated password reset requests to reach 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 6.2.2
Interim mitigation

Upgrade FortiMail to version 6.0.8, 6.2.3, 6.4.0 or later and FortiVoiceEnterprise to version 6.0.2 or later. Apply network segmentation to restrict management interface access from untrusted networks as an interim control.

Recommended fix Moderate confidence

FortiMail: 5.4.11+ / 6.0.8+ / 6.2.3+ | FortiVoice: 6.0.2+

  1. 1. Identify the currently installed FortiMail or FortiVoice version via the web UI (System > Status) or CLI: 'get system status'
  2. 2. For FortiMail: If running 5.4.x, upgrade to 5.4.11 or later; if running 6.0.x, upgrade to 6.0.8 or later; if running 6.2.x, upgrade to 6.2.3 or later
  3. 3. For FortiVoice: Upgrade from 6.0.0/6.0.1 to 6.0.2 or later
  4. 4. Download the firmware from the Fortinet Customer Support Portal (support.fortinet.com) after logging in with valid credentials
  5. 5. Upload the firmware via FortiMail/FortiVoice web UI: System > Maintenance > Firmware > Upload, or via CLI: 'execute firmware upgrade'
  6. 6. After upgrade, verify the version change and confirm the vulnerability is remediated
  7. 7. Review admin accounts and monitor for unauthorized access since this vulnerability allows unauthenticated password changes
Caveat Review release notes for any configuration or feature changes between versions; test in staging environment before production deployment

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

Fix this in Fortimail Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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