dbcve.org
FortiosOperating system · Fortinet

CVE-2022-22306

MEDIUM · 5.3 CVSS v3.1 Published 2022-05-24
Fix available
A fix is available. Upgrade to 6.4.9 or later.
See remediation →
58/100
Remediation priority · Elevated
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 certificate validation vulnerability [CWE-295] in FortiOS 6.0.0 through 6.0.14, 6.2.0 through 6.2.10, 6.4.0 through 6.4.8, 7.0.0 may allow a network adjacent and unauthenticated attacker to man-in-the-middle the communication between the FortiGate and some peers such as private SDNs and external cloud platforms.

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 · moderate confidence

FortiOS contains an improper certificate validation vulnerability (CWE-295) that allows a network-adjacent, unauthenticated attacker to perform man-in-the-middle attacks against communications between FortiGate devices and private SDNs or external cloud platforms.

MitigationUpgrade FortiOS to a patched version (7.0.1 or higher for 7.0.x branches, or the latest available patched version for 6.x branches). For temporary mitigation, ensure network segmentation limits adjacent attacker access.

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.14>= 6.2.0, <= 6.2.10>= 6.4.0, < 6.4.9= 7.0.0

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:H/PR:N/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. Check installed FortiOS version
    Run 'get system status' from the FortiGate CLI or check the dashboard in FortiManager. The output will display the firmware version under 'Version'.
    Affected if The version matches any of these ranges: 6.0.0 through 6.0.14, 6.2.0 through 6.2.10, 6.4.0 through 6.4.8, or exactly 7.0.0.
  2. Identify configured SDN connectors
    Run 'get system sdn-connector' from the CLI to list all configured SDN connectors (e.g., AWS, Azure, GCP, Kubernetes). Alternatively, check the GUI under Security Fabric > External Connectors.
    Affected if Any SDN connector is active and pointing to private SDNs or external cloud platforms.
  3. Identify cloud platform integrations
    Run 'get system cloud-init' and 'get system azure-application-gateway' (if applicable) or review the configuration under System > Feature Visibility for cloud-related features.
    Affected if The FortiGate is integrated with Azure, AWS, GCP, or other public cloud platforms for traffic inspection orSD-WAN.
  4. Check SSL inspection profiles for cloud traffic
    Run 'show firewall ssl-ssh-profile' to view SSL inspection profiles, particularly those applied to traffic destined for cloud services.
    Affected if SSL inspection is enabled for traffic to external cloud platforms or SDNs without proper certificate validation configured.

You are affected if your FortiOS version falls within 6.0.0-6.0.14, 6.2.0-6.2.10, 6.4.0-6.4.8, or 7.0.0 AND the device has active SDN connector or cloud platform integrations that rely on certificate validation.

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.4.9 or later
Fixed in 6.4.9
Interim mitigation

Upgrade FortiOS to a patched version (7.0.1 or higher for 7.0.x branches, or the latest available patched version for 6.x branches). For temporary mitigation, ensure network segmentation limits adjacent attacker access.

Recommended fix High confidence

FortiOS 6.0.15 (for 6.0.x), 6.2.11 (for 6.2.x), 6.4.9 (for 6.4.x), or 7.0.1+ (for 7.0.x)

  1. 1. Identify the current FortiOS version running on the FortiGate device using 'get system status' or via the web UI under Dashboard > Status
  2. 2. Determine the appropriate upgrade path based on current version branch (6.0.x, 6.2.x, 6.4.x, or 7.0.x)
  3. 3. Download the corresponding fixed firmware image from Fortinet Customer Support Portal or Fortiguard
  4. 4. Upload the firmware image via FortiGate web UI (System > Firmware) or CLI using 'execute upgrade'
  5. 5. Verify the upgrade was successful and the device is operational
  6. 6. Confirm the fix is applied by checking the version and reviewing the release notes for CVE-2022-22306
Caveat Review Fortinet release notes for each version for potential configuration or feature changes; test in non-production environment first

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

Fix this in Fortios Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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