dbcve.org
FortitesterApplication · Fortinet

CVE-2022-33870

HIGH · 7.8 CVSS v3.1 Published 2022-11-02
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
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
An improper neutralization of special elements used in an OS command vulnerability [CWE-78] in the command line interpreter of FortiTester 3.0.0 through 3.9.1, 4.0.0 through 4.2.0, 7.0.0 through 7.1.0 may allow an authenticated attacker to execute unauthorized commands via specifically crafted arguments to existing commands.

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
How this class of weakness works · CWE-78

User input reaches a shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.

General guidance for the os command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
FortitesterApplication
Affected:= 3.0.0= 3.1.0= 3.2.0= 3.3.0= 3.3.1= 3.4.0= 3.5.0= 3.5.1= 3.6.0= 3.7.0= 3.7.1= 3.8.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
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
Patch available Apply the vendor patch
Vendor patch fortiguard.com →
Recommended fix Moderate confidence

FortiTester version greater than 3.9.1, 4.2.0, or 7.1.0 (consult FG-IR-22-070 for the exact fixed release)

  1. 1. Identify the current FortiTester version installed in your environment
  2. 2. Review the FortiGuard PSIRT advisory at https://fortiguard.com/psirt/FG-IR-22-070 for the complete list of affected versions and fixed releases
  3. 3. Plan an upgrade to a FortiTester version beyond the vulnerable versions (after 3.9.1, 4.2.0, or 7.1.0 depending on your major version branch)
  4. 4. Before upgrading, backup all FortiTester configurations and test data
  5. 5. Schedule a maintenance window as the upgrade may require downtime
  6. 6. Perform the upgrade following FortiTester upgrade documentation
  7. 7. After upgrade, verify the system is operational and test that the specific command functionality works correctly
  8. 8. Confirm the new version is no longer vulnerable to CVE-2022-33870
Caveat Standard FortiTester upgrade considerations apply - review upgrade path documentation for any configuration migration requirements

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

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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