dbcve.org
FortinacApplication · Fortinet

CVE-2022-45858

HIGH · 7.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 9.1.0 / 9.2.6 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
A use of a weak cryptographic algorithm vulnerability [CWE-327] in FortiNAC 9.4.1 and below, 9.2.6 and below, 9.1.0 all versions, 8.8.0 all versions, 8.7.0 all versions may increase the chances of an attacker to have access to sensitive information or to perform man-in-the-middle attacks.

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 uses weak cryptographic algorithms in its communication channels, potentially allowing attackers to decrypt sensitive data or intercept communications via man-in-the-middle attacks. The vulnerability affects multiple version branches (8.7.x through 9.4.x).

MitigationUpgrade FortiNAC to a patched version as specified by Fortinet; verify that strong cryptographic algorithms (e.g., TLS 1.2+ with strong ciphers) are enforced in all communications.

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.7.0, < 9.1.0>= 9.2.0, < 9.2.6>= 9.4.0, < 9.4.2

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 FortiNAC version
    Access the FortiNAC administrative interface or CLI and retrieve the installed software version. This is typically found in the dashboard or via command 'get system status' in the CLI.
    Affected if The installed version falls within >= 8.7.0 and < 9.1.0, OR >= 9.2.0 and < 9.2.6, OR >= 9.4.0 and < 9.4.2.
  2. Locate SSL/TLS configuration settings
    Navigate to System Settings or Network Configuration in the FortiNAC web interface. Look for SSL/TLS, cipher suite, or protocol configuration sections.
    Affected if Weak cryptographic algorithms (such as TLS 1.0/1.1, weak cipher suites like RC4, 3DES, or NULL encryption) are enabled or selected.
  3. Verify communication channel encryption settings
    Check the configuration for management interfaces, API endpoints, and agent communications. Inspect settings related to 'SSL encryption', 'TLS version', or 'cipher list'.
    Affected if The configuration allows legacy or weak protocols (SSLv3, TLS 1.0, TLS 1.1) or permits insecure cipher suites.
  4. Review server certificate configuration
    Examine the SSL/TLS certificate settings on management ports and internal communication channels. Look for options labeled 'minimum protocol version' or 'allowed ciphers'.
    Affected if The minimum protocol version is set below TLS 1.2 or if 'high' security cipher suites are not enforced.

You are affected if your FortiNAC version is one of the vulnerable releases listed AND weak cryptographic algorithms (TLS 1.0/1.1, weak ciphers) are enabled in your SSL/TLS configuration.

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 9.1.0 / 9.2.6 / 9.4.2 or later
Fixed in 9.1.09.2.69.4.2
Interim mitigation

Upgrade FortiNAC to a patched version as specified by Fortinet; verify that strong cryptographic algorithms (e.g., TLS 1.2+ with strong ciphers) are enforced in all communications.

Recommended fix High confidence

FortiNAC 9.4.2 or later (or 9.2.6+ if staying on 9.2 branch)

  1. Identify current FortiNAC version by navigating to System > Settings > About in the FortiNAC management interface
  2. Backup current FortiNAC configuration before initiating upgrade
  3. Download the appropriate firmware image (FortiNAC 9.4.2 or later) from Fortinet Customer Support portal (https://support.fortinet.com)
  4. Upload the firmware image via System > Firmware in FortiNAC admin UI
  5. Initiate the upgrade and monitor the process for completion
  6. Verify successful upgrade by checking System > Settings > About shows version 9.4.2 or higher
  7. Confirm the vulnerability is resolved by reviewing the applied patches in the release notes
Caveat Review FortiNAC 9.4.2 release notes for any configuration changes or migration requirements; test upgrade in staging environment first

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

Fix this in Fortinac Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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