dbcve.org
FortiosOperating system · Fortinet

CVE-2020-29010

MEDIUM · 5.0 CVSS v3.1 Published 2025-03-17
Fix available
A fix is available. Upgrade to 6.0.11 / 6.2.5 or later.
See remediation →
56/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
An exposure of sensitive information to an unauthorized actor vulnerability in FortiOS version 6.2.4 and below, version 6.0.10 and belowmay allow remote authenticated actors to read the SSL VPN events log entries of users in other VDOMs by executing "get vpn ssl monitor" from the CLI. The sensitive data includes usernames, user groups, and IP address.

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

In FortiOS 6.2.4 and below and 6.0.10 and below, an authenticated user with access to one VDOM can execute 'get vpn ssl monitor' from the CLI to view SSL VPN event log entries belonging to users in other VDOMs. This exposes sensitive data including usernames, user groups, and source IP addresses to unauthorized cross-VDOM visibility.

MitigationUpgrade FortiOS to version 6.2.5 or 6.0.11 and above to remediate this vulnerability. Additionally, review VDOM isolation and user access controls to ensure proper segregation.

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
FortiosOperating system
Affected:>= 6.0.0, < 6.0.11>= 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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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. Check FortiOS version
    Run 'get system status' from the CLI or check the FortiGate web UI under System > Firmware. Note the exact version number displayed.
    Affected if The version is 6.0.0 through 6.0.10, or 6.2.0 through 6.2.4 (versions below 6.0.11 or 6.2.5).
  2. Verify VDOM is enabled
    Run 'get system vdom-status' from the CLI or check in the web UI under System > VDOM. Confirm if multiple VDOMs are configured.
    Affected if VDOMs are enabled and more than one VDOM exists on the device.
  3. Test cross-VDOM visibility with SSL VPN monitor
    Log in as a user with access to only one VDOM, then run 'get vpn ssl monitor' from the CLI. Review the output for event log entries belonging to users in other VDOMs.
    Affected if The output displays usernames, user groups, or source IP addresses from VDOMs other than the one the authenticated user is assigned to.

If FortiOS version is 6.0.0-6.0.10 or 6.2.0-6.2.4 AND VDOMs are enabled with multiple VDOMs present, then the environment is affected by this cross-VDOM information disclosure vulnerability.

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 6.0.11 / 6.2.5 or later
Fixed in 6.0.116.2.5
Interim mitigation

Upgrade FortiOS to version 6.2.5 or 6.0.11 and above to remediate this vulnerability. Additionally, review VDOM isolation and user access controls to ensure proper segregation.

Recommended fix High confidence

FortiOS 6.0.11 or later for 6.0.x branch; FortiOS 6.2.5 or later for 6.2.x branch

  1. Identify the currently installed FortiOS version and branch (6.0.x or 6.2.x) using 'get system status' command
  2. For FortiOS 6.0.x branch: Upgrade to version 6.0.11 or later
  3. For FortiOS 6.2.x branch: Upgrade to version 6.2.5 or later
  4. Alternatively, upgrade to the latest stable FortiOS version available from Fortinet support portal
  5. After upgrade, verify the fix by confirming 'get vpn ssl monitor' no longer exposes cross-VDOM user information
Caveat Review Fortinet release notes for the target version for any configuration or feature changes before upgrading

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

Fix this in Fortios 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-2020-29010 — 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-29010 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