dbcve.org
FortianalyzerApplication · Fortinet

CVE-2021-43072

MEDIUM · 6.7 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to 2.0.9 / 6.2.11 or later.
See remediation →
69/100
Remediation priority · Elevated
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 buffer copy without checking size of input ('classic buffer overflow') in Fortinet FortiAnalyzer version 7.0.2 and below, version 6.4.7 and below, version 6.2.9 and below, version 6.0.11 and below, version 5.6.11 and below, FortiManager version 7.0.2 and below, version 6.4.7 and below, version 6.2.9 and below, version 6.0.11 and below, version 5.6.11 and below, FortiOS version 7.0.0 through 7.0.4, 6.4.0 through 6.4.8, 6.2.0 through 6.2.10, 6.0.x and FortiProxy version 7.0.0 through 7.0.3, 2.0.0 through 2.0.8, 1.2.x, 1.1.x and 1.0.x allows attacker to execute unauthorized code or commands via crafted CLI `execute restore image` and `execute certificate remote` operations with the tFTP protocol.

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

Classic buffer overflow vulnerability in Fortinet FortiAnalyzer, FortiManager, FortiOS, and FortiProxy allows authenticated attackers to execute arbitrary code via crafted CLI commands (`execute restore image` and `execute certificate remote`) using the tFTP protocol without proper size validation on input buffers.

MitigationApply the vendor-supplied patches for affected versions (FortiOS 7.0.5+, 6.4.9+, 6.2.11+; FortiAnalyzer/FortiManager 7.0.3+, 6.4.8+, 6.2.10+, 6.0.12+, 5.6.12+; FortiProxy 7.0.4+, 2.0.9+). Restrict tFTP access to trusted networks and limit CLI access to authenticated, authorized personnel only.

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.4.8>= 7.0.0, < 7.0.3
FortimanagerApplication
Affected:>= 5.6.0, < 6.4.8>= 7.0.0, < 7.0.3
FortiproxyApplication
Affected:>= 1.0.0, < 2.0.9>= 7.0.0, < 7.0.4
FortiosOperating system
Affected:>= 6.0.0, < 6.2.11>= 6.4.0, < 6.4.9>= 7.0.0, < 7.0.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 the installed Fortinet product
    Run `get system status` or `show system` in CLI, or check the web UI dashboard for the product name (FortiOS, FortiAnalyzer, FortiManager, or FortiProxy)
    Affected if The product is one of FortiOS, FortiAnalyzer, FortiManager, or FortiProxy and matches affected version ranges below
  2. Determine the installed version number
    Run `get system status` in CLI to display the firmware version, or check the FortiManager/FortiAnalyzer web UI under System > Firmware
    Affected if The version falls within any of these ranges: FortiOS 6.0.0-6.2.10, 6.4.0-6.4.8, 7.0.0-7.0.5; FortiAnalyzer/FortiManager 5.6.0-6.2.9, 6.4.0-6.4.7, 7.0.0-7.0.2; FortiProxy 1.0.0-2.0.8, 7.0.0-7.0.3
  3. Verify if tFTP service is enabled or accessible
    Check system settings via `show system tftp` or review network configuration for tFTP service exposure. In FortiOS, run `get system interface` and review allowed protocols on management interfaces
    Affected if tFTP is enabled or accessible on management or WAN interfaces without proper network segmentation
  4. Confirm CLI access for untrusted or unauthorized users
    Review user accounts and privilege levels via `get system admin` or check FortiOS/FortiProxy user group definitions under User & Authentication
    Affected if Untrusted, low-privilege, or unauthorized users have CLI access permissions (especially via management interfaces)
  5. Check for use of vulnerable CLI commands
    Review audit logs or configuration for any use of `execute restore image` or `execute certificate remote` commands with tFTP source
    Affected if These specific CLI commands using tFTP protocol have been executed in the environment

The environment is affected if the installed Fortinet product is FortiOS, FortiAnalyzer, FortiManager, or FortiProxy with a version within the affected ranges AND tFTP is accessible while allowing CLI commands to untrusted users.

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 2.0.9 / 6.2.11 / 6.4.8 or later
Fixed in 2.0.96.2.116.4.8
Interim mitigation

Apply the vendor-supplied patches for affected versions (FortiOS 7.0.5+, 6.4.9+, 6.2.11+; FortiAnalyzer/FortiManager 7.0.3+, 6.4.8+, 6.2.10+, 6.0.12+, 5.6.12+; FortiProxy 7.0.4+, 2.0.9+). Restrict tFTP access to trusted networks and limit CLI access to authenticated, authorized personnel only.

Recommended fix High confidence

FortiOS 7.0.6+ / 6.4.9+ / 6.2.11+ | FortiAnalyzer 7.0.3+ / 6.4.8+ | FortiManager 7.0.3+ / 6.4.8+ | FortiProxy 7.0.4+ / 2.0.9+

  1. 1. Identify the exact Fortinet product (FortiOS, FortiAnalyzer, FortiManager, or FortiProxy) and current version running in your environment
  2. 2. For FortiOS: Upgrade to version 7.0.6 or later for 7.0.x deployments; upgrade to 6.4.9 or later for 6.4.x deployments; upgrade to 6.2.11 or later for 6.2.x deployments
  3. 3. For FortiAnalyzer: Upgrade to version 7.0.3 or later for 7.0.x deployments; upgrade to 6.4.8 or later for 6.4.x deployments
  4. 4. For FortiManager: Upgrade to version 7.0.3 or later for 7.0.x deployments; upgrade to 6.4.8 or later for 6.4.x deployments
  5. 5. For FortiProxy: Upgrade to version 7.0.4 or later for 7.0.x deployments; upgrade to 2.0.9 or later for 2.0.x deployments
  6. 6. After upgrade, verify the system is functioning normally and review audit logs for any suspicious tFTP operations
  7. 7. Consider restricting tFTP protocol access via access profiles and administrative access lists as a defense-in-depth measure
Caveat Upgrading firmware carries inherent risk; ensure backups and rollback procedures are in place; test in staging environment before production deployment

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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