dbcve.org
FortiadcApplication · Fortinet

CVE-2022-22299

HIGH · 7.8 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 6.4.8 / 7.0.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 format string vulnerability [CWE-134] in the command line interpreter of FortiADC version 6.0.0 through 6.0.4, FortiADC version 6.1.0 through 6.1.5, FortiADC version 6.2.0 through 6.2.1, FortiProxy version 1.0.0 through 1.0.7, FortiProxy version 1.1.0 through 1.1.6, FortiProxy version 1.2.0 through 1.2.13, FortiProxy version 2.0.0 through 2.0.7, FortiProxy version 7.0.0 through 7.0.1, FortiOS version 6.0.0 through 6.0.14, FortiOS version 6.2.0 through 6.2.10, FortiOS version 6.4.0 through 6.4.8, FortiOS version 7.0.0 through 7.0.2, FortiMail version 6.4.0 through 6.4.5, FortiMail version 7.0.0 through 7.0.2 may allow an authenticated user to execute unauthorized code or commands 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

A detailed technical summary for this CVE is being prepared.

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
FortiadcApplication
Affected:>= 6.0.0, <= 6.0.4>= 6.1.0, <= 6.1.6= 6.2.0= 6.2.1
FortimailApplication
Affected:>= 6.4.0, <= 6.4.5>= 7.0.0, <= 7.0.2
FortiproxyApplication
Affected:>= 1.0.0, <= 1.0.7>= 1.1.0, <= 1.1.6>= 1.2.0, <= 1.2.13>= 2.0.0, <= 2.0.7= 7.0.0= 7.0.1
FortiosOperating system
Affected:>= 5.0.0, <= 5.0.14>= 5.2.0, <= 5.2.15>= 5.4.0, <= 5.4.13>= 5.6.0, <= 5.6.14>= 6.0.0, <= 6.0.14>= 6.2.0, <= 6.2.10>= 6.4.0, < 6.4.8>= 7.0.0, < 7.0.2

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 6.4.8 / 7.0.2 or later
Fixed in 6.4.87.0.2
Vendor patch fortiguard.com →
Recommended fix High confidence

Upgrade to the first version release after your current affected branch (e.g., FortiADC 6.0.5+, FortiOS 6.0.15+, FortiProxy 7.0.2+, FortiMail 7.0.3+)

  1. 1. Identify the exact Fortinet product (FortiADC, FortiMail, FortiProxy, or FortiOS) and current version running in your environment
  2. 2. For FortiADC: Upgrade to version 6.0.5 or later (if on 6.0.x), 6.1.6 or later (if on 6.1.x), or 6.2.2 or later (if on 6.2.x)
  3. 3. For FortiMail: Upgrade to version 6.4.6 or later (if on 6.4.x) or 7.0.3 or later (if on 7.0.x)
  4. 4. For FortiProxy: Upgrade to version 1.0.8 or later (if on 1.0.x), 1.1.7 or later (if on 1.1.x), 1.2.14 or later (if on 1.2.x), 2.0.8 or later (if on 2.0.x), or 7.0.2 or later (if on 7.0.x)
  5. 5. For FortiOS: Upgrade to version 5.0.15 or later (if on 5.0.x), 5.2.16 or later (if on 5.2.x), 5.4.14 or later (if on 5.4.x), 5.6.15 or later (if on 5.6.x), 6.0.15 or later (if on 6.0.x), 6.2.11 or later (if on 6.2.x), 6.4.9 or later (if on 6.4.x), or 7.0.3 or later (if on 7.0.x)
  6. 6. Before upgrading, review Fortinet release notes for the target version to ensure compatibility with your configuration
  7. 7. After upgrade, verify the system is functioning correctly and the vulnerability is resolved
  8. 8. If immediate upgrade is not possible, limit CLI access to trusted users only and monitor for suspicious command activity
Caveat Review release notes for your specific product model before upgrading as minor version upgrades may introduce configuration or compatibility changes

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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