dbcve.org
FortinacApplication · Fortinet

CVE-2023-22633

HIGH · 7.5 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to after 9.2.6 or later.
See remediation →
84/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
An improper permissions, privileges, and access controls vulnerability [CWE-264] in FortiNAC-F 7.2.0, FortiNAC 9.4.1 and below, 9.2.6 and below, 9.1.8 and below, 8.8.0 all versions 8.7.0 all versions may allow an unauthenticated attacker to perform a DoS attack on the device via client-secure renegotiation.

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

This vulnerability in FortiNAC allows unauthenticated remote attackers to cause Denial of Service via client-secure renegotiation. The issue stems from improper access control (CWE-264) that fails to properly validate or limit renegotiation requests, potentially exhausting device resources.

MitigationApply vendor-supplied patches/updates to upgrade FortiNAC to a fixed version beyond 9.4.1, 9.2.6, 9.1.8, or the fixed FortiNAC-F 7.2.0 release. Until patched, consider network segmentation or rate-limiting TLS connections as compensating controls.

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, <= 8.7.6>= 8.8.0, <= 8.8.11>= 9.1.0, <= 9.1.8>= 9.2.0, <= 9.2.6= 9.4.0= 9.4.1
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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 installation type
    Determine whether you are running FortiNAC (appliance/software) or FortiNAC-F by checking your product model documentation or license information.
    Affected if The system is FortiNAC version 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.8, 9.2.0-9.2.6, 9.4.0, 9.4.1, or FortiNAC-F version 7.2.0.
  2. Determine installed FortiNAC version
    Log into the FortiNAC CLI and run the command 'get system status' or check the web UI dashboard for the firmware version displayed.
    Affected if The displayed version matches any of the affected version ranges listed for this CVE.
  3. Verify management interface exposure
    Check network configuration to determine if FortiNAC management interfaces (web UI on ports 443/80, SSH on port 22, or other admin services) are reachable from untrusted or external networks.
    Affected if Any FortiNAC administrative interface is exposed to the internet or untrusted internal networks without proper firewall filtering.
  4. Confirm TLS renegotiation is enabled
    Review FortiNAC SSL/TLS settings in the web UI under System Settings > SSL Settings or via CLI 'get system interface' to verify secure renegotiation is not explicitly disabled.
    Affected if TLS renegotiation is permitted on exposed management interfaces and the installed version is within the affected ranges.

You are affected if your FortiNAC version falls within 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.8, 9.2.0-9.2.6, 9.4.0-9.4.1, or FortiNAC-F 7.2.0 AND the management interface is reachable from untrusted networks.

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 a release after 9.2.6
Interim mitigation

Apply vendor-supplied patches/updates to upgrade FortiNAC to a fixed version beyond 9.4.1, 9.2.6, 9.1.8, or the fixed FortiNAC-F 7.2.0 release. Until patched, consider network segmentation or rate-limiting TLS connections as compensating controls.

Fix this in Fortinac Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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