dbcve.org
FortinacApplication · Fortinet

CVE-2022-40675

HIGH · 7.4 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 7.2.0 / 9.4.2 or later.
See remediation →
83/100
Remediation priority · High
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
Some cryptographic issues in Fortinet FortiNAC versions 9.4.0 through 9.4.1, 9.2.0 through 9.2.7, 9.1.0 through 9.1.8, 8.8.0 through 8.8.11, 8.7.0 through 8.7.6, 8.6.0 through 8.6.5, 8.5.0 through 8.5.4, 8.3.7 may allow an attacker to decrypt and forge protocol communication messages.

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

FortiNAC contains cryptographic weaknesses in its protocol communication implementation that allow attackers to decrypt existing communications and forge new protocol messages. The specific cryptographic flaws (likely weak encryption or improper validation) affect multiple version branches across the 8.x and 9.x release trains.

MitigationUpgrade FortiNAC to the vendor-provided patched version that addresses these cryptographic vulnerabilities; for versions not receiving patches, consider network segmentation and restricting access to the management interface.

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
FortinacApplication
Affected:>= 8.3.7, <= 9.2.7>= 9.4.0, < 9.4.2
Fortinac FApplication
Affected:< 7.2.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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 if FortiNAC is deployed
    Locate FortiNAC installations in your environment by checking for Fortinet FortiNAC software or appliance installations on your network.
    Affected if FortiNAC or FortiNAC F software/appliance is present in the environment
  2. Determine installed FortiNAC version
    Access the FortiNAC CLI or GUI and run the command to display the system version, typically via 'get system status' or checking the GUI dashboard for the firmware version.
    Affected if Unable to retrieve version information for comparison
  3. Check FortiNAC version against affected ranges
    Compare the installed version to the affected ranges: 8.3.7 through 9.2.7 (inclusive), or 9.4.0 through 9.4.1 (inclusive). Versions outside these ranges are not affected by this CVE.
    Affected if Installed version falls within >= 8.3.7 <= 9.2.7 OR >= 9.4.0 < 9.4.2
  4. Check FortiNAC F version separately
    If using FortiNAC F model, check its specific firmware version using the appliance management interface or CLI 'get system status' command.
    Affected if FortiNAC F version is less than 7.2.0
  5. Verify protocol communication features are in use
    FortiNAC must have its protocol communication capabilities active for this vulnerability to be exploitable. Check if client-server communications or integration with network access control are enabled in the FortiNAC configuration.
    Affected if Protocol communication features are enabled and the version is within affected ranges

Environment is affected if FortiNAC or FortiNAC F is deployed AND the installed version falls within the affected ranges (8.3.7-9.2.7, 9.4.0-9.4.1 for FortiNAC, or < 7.2.0 for FortiNAC F).

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 7.2.0 / 9.4.2 or later
Fixed in 7.2.09.4.2
Interim mitigation

Upgrade FortiNAC to the vendor-provided patched version that addresses these cryptographic vulnerabilities; for versions not receiving patches, consider network segmentation and restricting access to the management interface.

Recommended fix High confidence

FortiNAC: upgrade to 9.4.2 or later; FortiNAC F: upgrade to 7.2.0 or later

  1. 1. Identify the currently installed FortiNAC version by checking the system information or using the CLI command: `get system status`
  2. 2. For FortiNAC (FortiNAC): If running version 9.4.0 or 9.4.1, upgrade to version 9.4.2 or later
  3. 3. For FortiNAC (FortiNAC): If running version 9.2.0 through 9.2.7, upgrade to version 9.4.2 or later (or the latest supported version)
  4. 4. For FortiNAC (FortiNAC): If running version 9.1.0 through 9.1.8, 8.8.0 through 8.8.11, 8.7.0 through 8.7.6, 8.6.0 through 8.6.5, 8.5.0 through 8.5.4, or 8.3.7, upgrade to version 9.4.2 or later
  5. 5. For FortiNAC F: If running any version prior to 7.2.0, upgrade to version 7.2.0 or later
  6. 6. Download the appropriate firmware from the Fortinet Customer Support portal or FortiGuard
  7. 7. Backup the current configuration before upgrading
  8. 8. Upload and install the new firmware following Fortinet's upgrade procedures
Caveat Review Fortinet release notes for version 9.4.2 and subsequent releases for any configuration or feature changes that may affect existing deployments

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

Fix this in Fortinac Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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