dbcve.org
FortinacApplication · Fortinet

CVE-2022-45860

HIGH · 7.5 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 9.4.2 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
A weak authentication vulnerability [CWE-1390] in FortiNAC-F version 7.2.0, FortiNAC version 9.4.2 and below, 9.2 all versions, 9.1 all versions, 8.8 all versions, 8.7 all versions in device registration page may allow an unauthenticated attacker to perform password spraying attacks with an increased chance of success.

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

A weak authentication vulnerability in FortiNAC's device registration page allows unauthenticated attackers to perform password spraying attacks with increased success probability. The vulnerability affects the authentication mechanism on this specific web interface, enabling attackers to systematically attempt passwords without proper rate limiting or account lockout protections.

MitigationUpgrade FortiNAC to a patched version beyond 9.4.2 (for 9.x) and 8.7 (for 8.x). Additionally, implement network segmentation to limit exposure of the device registration page to untrusted networks and consider implementing WAF rules or IP rate limiting 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, <= 9.2.6>= 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/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 FortiNAC version via CLI
    Log into FortiNAC CLI and run: `get system status` or `fnsysctl get system version` to retrieve the installed version number
    Affected if Version matches >= 8.7.0 AND <= 9.2.6, OR >= 9.4.0 AND < 9.4.2, OR equals 7.2.0 (for FortiNAC F model)
  2. Identify device registration page exposure
    Determine if the FortiNAC web interface (port 8443 or 8080) is accessible from untrusted/low-trust networks. Check firewall rules or perform an external port scan from an untrusted network: `nmap -p 8443,8080 <external-ip>`
    Affected if Device registration page is reachable from untrusted networks without authentication
  3. Check for rate limiting on authentication endpoints
    Review FortiNAC GUI under System > Config > Authentication > Security Settings or check CLI: `get system interface` to identify web service ports, then verify if rate-limit or account-lockout policies are configured
    Affected if No rate limiting or account lockout is configured for the device registration authentication endpoint

User is affected if FortiNAC version falls within the vulnerable ranges AND the device registration page is exposed to untrusted networks without compensating rate-limit controls.

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.4.2 or later
Fixed in 9.4.2
Interim mitigation

Upgrade FortiNAC to a patched version beyond 9.4.2 (for 9.x) and 8.7 (for 8.x). Additionally, implement network segmentation to limit exposure of the device registration page to untrusted networks and consider implementing WAF rules or IP rate limiting as compensating controls.

Recommended fix High confidence

FortiNAC: upgrade to 9.4.2 or later; FortiNAC-F: contact Fortinet support

  1. 1. Identify the current FortiNAC or FortiNAC-F version running in your environment
  2. 2. For FortiNAC: Upgrade to version 9.4.2 or later to remediate the weak authentication vulnerability
  3. 3. For FortiNAC-F version 7.2.0: Contact Fortinet support for specific patch guidance or migration options
  4. 4. After upgrade, verify the device registration page authentication behavior
  5. 5. Monitor logs for any suspicious password spraying activity

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

Fix this in Fortinac Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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