dbcve.org
FortiproxyApplication · Fortinet

CVE-2020-6648

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to 1.2.10 / 6.0.12 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 cleartext storage of sensitive information vulnerability in FortiOS command line interface in versions 6.2.4 and earlier and FortiProxy 2.0.0, 1.2.9 and earlier may allow an authenticated attacker to obtain sensitive information such as users passwords by connecting to FortiGate CLI and executing the "diag sys ha checksum show" command.

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

FortiOS and FortiProxy contain a cleartext storage vulnerability where sensitive information such as user passwords can be retrieved in cleartext by an authenticated attacker executing the 'diag sys ha checksum show' command via the CLI.

MitigationUpgrade FortiOS to version 6.2.5 or later and FortiProxy to version 1.2.10 or later to receive the patch for this vulnerability.

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
FortiproxyApplication
Affected:< 1.2.10= 2.0.0
FortiosOperating system
Affected:< 6.0.12>= 6.2.0, < 6.2.5

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 product and version
    Log into the FortiOS/FortiProxy CLI and execute 'get system status' to retrieve the firmware version and product name
    Affected if The displayed firmware version falls within FortiOS < 6.0.12, FortiOS 6.2.0-6.2.4, FortiProxy < 1.2.10, or FortiProxy = 2.0.0
  2. Verify CLI access exists
    Confirm you have administrative CLI access to the device via console, SSH, or telnet
    Affected if CLI access is available to any user account, allowing execution of the 'diag sys ha checksum show' command
  3. Check HA checksum command output
    Execute the command 'diag sys ha checksum show' in the CLI and examine the output for any cleartext sensitive information such as user passwords or other credentials
    Affected if The command returns cleartext sensitive data that should have been obscured or encrypted

You are affected if your FortiOS or FortiProxy version is within the vulnerable ranges listed and an authenticated user can access the CLI to run the diagnostic command and view sensitive data in cleartext.

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 1.2.10 / 6.0.12 / 6.2.5 or later
Fixed in 1.2.106.0.126.2.5
Interim mitigation

Upgrade FortiOS to version 6.2.5 or later and FortiProxy to version 1.2.10 or later to receive the patch for this vulnerability.

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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