dbcve.org
FortinacApplication · Fortinet

CVE-2022-43951

HIGH · 7.5 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 7.2.0 / 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
An exposure of sensitive information to an unauthorized actor vulnerability [CWE-200] in FortiNAC 9.4.1 and below, 9.2.6 and below, 9.1.8 and below, 8.8.11 and below, 8.7.6 and below may allow an unauthenticated attacker to access sensitive information via crafted HTTP requests.

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

An unauthenticated attacker can access sensitive information in FortiNAC through crafted HTTP requests, exploiting an information disclosure vulnerability (CWE-200). The vulnerability exists in multiple version branches of FortiNAC (8.7.x, 8.8.x, 9.1.x, 9.2.x, 9.4.x) and allows unauthorized access to sensitive data without authentication.

MitigationUpgrade FortiNAC to version 9.4.2 or above, 9.2.7 or above, 9.1.9 or above, 8.8.12 or above, or 8.7.7 or above as specified in the Fortinet advisory.

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.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
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. Identify FortiNAC version
    Log into the FortiNAC CLI or web UI and navigate to the Dashboard or System > Settings to view the firmware version. Alternatively, check the /var/opt/VERSION file or run 'get system status' command in CLI.
    Affected if The installed 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, or 9.4.0-9.4.1 for FortiNAC; or is below 7.2.0 for FortiNAC F.
  2. Confirm HTTP/HTTPS web interface is accessible
    Attempt to access the FortiNAC web interface from an external or untrusted network by browsing to the device IP or hostname on ports 80 or 443. Verify the login page loads without authentication.
    Affected if The web interface is exposed to untrusted networks without IP restrictions, allowing unauthenticated HTTP requests to reach the device.
  3. Check management interface exposure
    Review the network configuration in FortiNAC under System > Network > Interfaces to determine which interfaces have management services (HTTP/HTTPS) enabled and their accessibility scope.
    Affected if Management interface with HTTP/HTTPS is bound to an interface accessible from untrusted networks (such as WAN or untrusted VLANs).

You are affected if your FortiNAC version is 8.7.0-8.7.6, 8.8.0-8.8.11, 9.1.0-9.1.8, 9.2.0-9.2.6, or 9.4.0-9.4.1 (or FortiNAC F below 7.2.0) AND the HTTP/HTTPS web interface is accessible from an untrusted network without authentication.

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 version 9.4.2 or above, 9.2.7 or above, 9.1.9 or above, 8.8.12 or above, or 8.7.7 or above as specified in the Fortinet advisory.

Recommended fix High confidence

FortiNAC 9.4.2+, 9.2.8+, 9.1.9+, 8.8.12+, 8.7.7+ | FortiNAC F 7.2.0+

  1. 1. Identify the current FortiNAC version by navigating to System > Settings > About in the FortiNAC admin UI or running 'fnsysctl get system status' on the CLI.
  2. 2. Determine which version branch is currently in use (9.4.x, 9.2.x, 9.1.x, 8.8.x, or 8.7.x for FortiNAC; or FortiNAC F version).
  3. 3. For FortiNAC version 9.4.0 or 9.4.1: Upgrade to version 9.4.2 or later.
  4. 4. For FortiNAC version 9.2.7 or earlier: Upgrade to version 9.2.8 or later.
  5. 5. For FortiNAC version 9.1.8 or earlier: Upgrade to version 9.1.9 or later.
  6. 6. For FortiNAC version 8.8.11 or earlier: Upgrade to version 8.8.12 or later.
  7. 7. For FortiNAC version 8.7.6 or earlier: Upgrade to version 8.7.7 or later.
  8. 8. For FortiNAC F versions below 7.2.0: Upgrade to version 7.2.0 or later.
Caveat Review FortiNAC release notes for the target version for any configuration or feature changes that may require adjustment

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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