dbcve.org
FortiwebApplication · Fortinet

CVE-2022-22297

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-07
Fix available
A fix is available. Upgrade to after 6.4.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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 incomplete filtering of one or more instances of special elements vulnerability [CWE-792] in the command line interpreter of FortiWeb version 6.4.0 through 6.4.1, FortiWeb version 6.3.0 through 6.3.17, FortiWeb all versions 6.2, FortiWeb all versions 6.1, FortiWeb all versions 6.0, FortiRecorder version 6.4.0 through 6.4.3, FortiRecorder all versions 6.0, FortiRecorder all versions 2.7 may allow an authenticated user to read arbitrary files via specially crafted command arguments.

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 is an incomplete input filtering vulnerability (CWE-792) in the command line interpreter of FortiWeb and FortiRecorder. An authenticated user can read arbitrary files on the system by providing specially crafted arguments to CLI commands, likely exploiting path traversal or injection through unfiltered special elements.

MitigationApply vendor-supplied patches/updates for FortiWeb and FortiRecorder. If patches are unavailable, restrict CLI access to trusted users only and monitor for unusual command patterns.

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
FortiwebApplication
Affected:>= 6.0.0, <= 6.0.8>= 6.1.0, <= 6.1.3>= 6.2.0, <= 6.2.7>= 6.3.0, <= 6.3.17>= 6.4.0, <= 6.4.3
Fortirecorder FirmwareOperating system
Affected:>= 2.7.0, <= 2.7.7>= 6.0.0, <= 6.0.12>= 6.4.0, <= 6.4.3

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 the Fortinet product and firmware version
    Access the CLI or web UI and run: 'get system status' for FortiWeb or 'fwc -v' for FortiRecorder. Alternatively, check the web UI System > FortiView > Dashboard under System Information.
    Affected if The product is FortiWeb or FortiRecorder and the version falls within these ranges: FortiWeb 6.0.0-6.0.8, 6.1.0-6.1.3, 6.2.0-6.2.7, 6.3.0-6.3.17, or 6.4.0-6.4.3; FortiRecorder 2.7.0-2.7.7, 6.0.0-6.0.12, or 6.4.0-6.4.3.
  2. Confirm CLI access is enabled
    In FortiWeb web UI, go to System > Admin > Administrators to verify CLI-based admin accounts exist. For FortiRecorder, check Admin > Admin Users. The vulnerability requires authenticated CLI access to be exploitable.
    Affected if CLI administrator accounts are present and the CLI interface (SSH or console) is accessible.
  3. Review recent CLI login activity
    In FortiWeb, run 'execute log display' or check the web UI Log & Report > Log Access > Event. Look for SSH or console login events. In FortiRecorder, check System Logs for admin login records.
    Affected if Unrecognized or suspicious CLI login events from unexpected IP addresses or users are found.
  4. Audit CLI command logs for path traversal patterns
    Search logs for CLI commands containing sequences like '../', '..\', or unusual file path arguments to built-in commands. Use 'execute log filter' to isolate CLI command execution events.
    Affected if CLI commands contain suspicious path traversal sequences or unexpected file read operations.

You are affected if the device runs FortiWeb or FortiRecorder with a version in the affected ranges AND the CLI interface is accessible to unauthorized or compromised authenticated users.

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

Apply vendor-supplied patches/updates for FortiWeb and FortiRecorder. If patches are unavailable, restrict CLI access to trusted users only and monitor for unusual command patterns.

Recommended fix Moderate confidence

FortiWeb: 6.0.9+, 6.1.4+, 6.2.8+, 6.3.18+, 6.4.2+ | FortiRecorder: 2.7.8+, 6.0.13+, 6.4.4+

  1. 1. Identify the current FortiWeb/FortiRecorder version by running: get system status
  2. 2. For FortiWeb: If running version 6.0.0-6.0.8, upgrade to 6.0.9 or later
  3. 3. For FortiWeb: If running version 6.1.0-6.1.3, upgrade to 6.1.4 or later
  4. 4. For FortiWeb: If running version 6.2.0-6.2.7, upgrade to 6.2.8 or later
  5. 5. For FortiWeb: If running version 6.3.0-6.3.17, upgrade to 6.3.18 or later
  6. 6. For FortiRecorder: If running version 2.7.0-2.7.7, upgrade to 2.7.8 or later
  7. 7. For FortiRecorder: If running version 6.0.0-6.0.12, upgrade to 6.0.13 or later
  8. 8. For FortiRecorder: If running version 6.4.0-6.4.3, upgrade to 6.4.4 or later
Caveat Standard Fortinet upgrade - review release notes for migration considerations between major version branches

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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