Fortiextender FirmwareOperating system · Fortinet
CVE-2022-23447
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 · uneditedAn improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability [CWE-22] in FortiExtender management interface 7.0.0 through 7.0.3, 4.2.0 through 4.2.4, 4.1.1 through 4.1.8, 4.0.0 through 4.0.2, 3.3.0 through 3.3.2, 3.2.1 through 3.2.3, 5.3 all versions may allow an unauthenticated and remote attacker to retrieve arbitrary files from the underlying filesystem via specially crafted web 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 · high confidenceA path traversal vulnerability in FortiExtender management interface allows unauthenticated remote attackers to craft web requests with directory traversal sequences (e.g., '../') to read arbitrary files from the filesystem. The affected versions span multiple branches (7.0.x, 4.x, 3.x, 5.3) of the FortiExtender firmware.
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
Fortiextender FirmwareOperating system
>= 3.2.1, < 3.2.4>= 3.3.0, < 3.3.3>= 4.0.0, < 4.0.3>= 4.1.1, < 4.1.9>= 4.2.0, < 4.2.5>= 7.0.0, < 7.0.4= 5.3.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiExtender firmware versionAccess the FortiExtender GUI or CLI and navigate to the Dashboard or System > Firmware to view the current installed version. Alternatively, run the command 'get system status' via CLI to retrieve the firmware version.Affected if The installed version falls within any of these ranges: >= 3.2.1 and < 3.2.4; >= 3.3.0 and < 3.3.3; >= 4.0.0 and < 4.0.3; >= 4.1.1 and < 4.1.9; >= 4.2.0 and < 4.2.5; >= 7.0.0 and < 7.0.4; or version 5.3.2 exactly.
-
Determine management interface exposureReview network configuration to determine if the FortiExtender management interface (HTTP/HTTPS ports) is reachable from untrusted or external networks. Check firewall policies, NAT rules, and interface assignments using 'show system interface' and review access control lists.Affected if The management interface IP or port is accessible from networks outside the trusted administrative zone, making it exploitable by unauthenticated remote attackers.
-
Inspect web logs for path traversal attemptsAccess FortiExtender logs via the GUI (Log & Report > Web Traffic) or CLI using 'execute log filter' and 'execute log display' to review HTTP requests. Search for patterns containing '../', '..%2F', URL-encoded traversal sequences, or requests to sensitive paths like /etc/passwd.Affected if Log entries show incoming requests containing directory traversal sequences targeting the management interface, indicating possible exploitation attempts.
-
Review system logs for unauthorized file accessCheck FortiExtender event and system logs for indicators of file read operations. Use CLI commands like 'execute log filter' with category 'event' and review for anomalies or unauthorized access events.Affected if Logs contain evidence of unexpected file read operations or access to system files that were not initiated by legitimate administrators.
You are affected if your FortiExtender firmware version is within the vulnerable ranges AND the management interface is accessible from untrusted networks, allowing unauthenticated path traversal attacks.
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 · scoped3.2.43.3.34.0.3
Upgrade to FortiExtender patched versions (7.0.4, 4.2.5, 4.1.9, 4.0.3, 3.3.3, 2.3.4) or later. If immediate patching is not possible, restrict network access to the management interface using firewall rules or ACLs to prevent unauthorized external access.
FortiExtender firmware 3.2.4, 3.3.3, 4.0.3, 4.1.9, 4.2.5, 7.0.4 or later depending on your current branch
- 1. Identify the current FortiExtender firmware version by logging into the FortiExtender management interface or running 'get system status' via CLI
- 2. Navigate to the Fortinet Support Portal (support.fortinet.com) and download the appropriate fixed firmware for your model
- 3. For affected version 3.2.1-3.2.3, upgrade to firmware version 3.2.4 or later
- 4. For affected version 3.3.0-3.3.2, upgrade to firmware version 3.3.3 or later
- 5. For affected version 4.0.0-4.0.2, upgrade to firmware version 4.0.3 or later
- 6. For affected version 4.1.1-4.1.8, upgrade to firmware version 4.1.9 or later
- 7. For affected version 4.2.0-4.2.4, upgrade to firmware version 4.2.5 or later
- 8. For affected version 7.0.0-7.0.3, upgrade to firmware version 7.0.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiextender Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23447 — 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-23447 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