FortinacApplication · Fortinet
CVE-2022-39952
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 · uneditedA external control of file name or path in Fortinet FortiNAC versions 9.4.0, 9.2.0 through 9.2.5, 9.1.0 through 9.1.7, 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 unauthenticated attacker to execute unauthorized code or commands via specifically crafted HTTP request.
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 confidenceExternal control of file name or path vulnerability (CWE-73) in Fortinet FortiNAC allows unauthenticated remote code execution via specifically crafted HTTP requests. The CVSS 9.8 indicates a network-exploitable, low-complexity attack requiring no authentication, affecting multiple version branches from 8.3.7 through 9.4.0.
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
>= 8.3.7, <= 8.8.9>= 9.1.0, < 9.1.8>= 9.2.0, < 9.2.6>= 9.4.0, < 9.4.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiNAC installed versionAccess the FortiNAC administrative UI or CLI and navigate to System > Settings > About, or run 'get system status' in the CLI to retrieve the firmware version.Affected if The installed version falls within any of these ranges: 8.3.7 through 8.8.9, 9.1.0 through 9.1.7, 9.2.0 through 9.2.5, or 9.4.0.
-
Verify HTTP management interface accessibilityAttempt to reach the FortiNAC management interface over HTTP/HTTPS from an untrusted network. Check firewall rules and interface bindings to confirm whether port 443 or 8080 is listening on non-internal interfaces.Affected if The management interface is accessible from untrusted networks without VPN or IP restriction.
-
Inspect exposed network servicesRun a port scan against the FortiNAC appliance targeting ports 80, 443, and 8080 to identify exposed HTTP services. Use 'nmap -p 80,443,8080 <target>' from an external perspective.Affected if HTTP services are listening on interfaces reachable from outside the trusted network.
-
Review WAF or filter rules for HTTP request patternsExamine any web application firewall or intrusion detection logs for attempts to exploit path traversal in HTTP requests to FortiNAC endpoints, particularly those involving file upload or download parameters.Affected if No WAF rules exist to filter suspicious HTTP request patterns targeting the FortiNAC web interface.
You are affected if your FortiNAC version falls within the vulnerable ranges (8.3.7-8.8.9, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.4.0) AND the management interface is reachable from untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.1.89.2.69.4.1
Upgrade FortiNAC to a fixed version beyond the affected branches; if immediate patching is not possible, restrict network access to the management interface and implement WAF rules to filter malicious HTTP requests.
FortiNAC 9.4.1 (or latest 9.4.x); FortiNAC 9.2.6 (or latest 9.2.x); FortiNAC 9.1.8 (or latest 9.1.x); FortiNAC 8.8.10+
- 1. Identify the currently installed FortiNAC version via the web UI (System > Settings > General > System Management) or CLI (get system status)
- 2. Based on your current major version, upgrade to the first fixed release: For FortiNAC 9.4.x, upgrade to 9.4.1 or later; For FortiNAC 9.2.x, upgrade to 9.2.6 or later; For FortiNAC 9.1.x, upgrade to 9.1.8 or later; For FortiNAC 8.8.x, upgrade to 8.8.10 or later
- 3. Download the firmware from Fortinet Customer Support portal (https://support.fortinet.com)
- 4. Backup the FortiNAC configuration before upgrade
- 5. Upload and install the new firmware via the web UI (System > Settings > Firmware) or CLI (execute firmware upgrade)
- 6. After upgrade, verify the new version is installed and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortinac
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39952 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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