FortitesterApplication · Fortinet
CVE-2022-33873
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 neutralization of special elements used in an OS Command ('OS Command Injection') vulnerabilities [CWE-78] in Console login components of FortiTester 2.3.0 through 3.9.1, 4.0.0 through 4.2.0, 7.0.0 through 7.1.0 may allow an unauthenticated attacker to execute arbitrary command in the underlying shell.
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 confidenceOS command injection vulnerability in FortiTester's console login component allows unauthenticated attackers to execute arbitrary shell commands due to improper neutralization of special elements in user input.
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
FortitesterApplication
>= 2.3.0, < 3.9.2>= 4.0.0, < 4.2.1>= 7.0.0, < 7.1.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 FortiTester installationLocate FortiTester appliances or virtual machines in your environment. Check for devices named 'FortiTester' or running FortiTester software in your asset inventory or network scan results.Affected if FortiTester is present in your environment
-
Determine installed FortiTester versionAccess the FortiTester console or admin interface and navigate to the System Settings or About page to view the firmware/version information. Alternatively, check the boot loader screen during startup or use SNMP/management APIs if available.Affected if The version cannot be determined or is one of: 2.3.0 to 3.9.1, 4.0.0 to 4.2.0, or 7.0.0 to 7.1.0
-
Verify console login interface accessibilityDetermine if the FortiTester management or console login interface (typically ports 443, 80, or SSH) is exposed to untrusted networks. Check firewall rules, ACLs, and VPN configurations restricting access to FortiTester management ports.Affected if The console login interface is accessible from untrusted or external networks without additional authentication barriers
You are affected if FortiTester is running a version within 2.3.0-3.9.1, 4.0.0-4.2.0, or 7.0.0-7.1.0 and its console login interface is network-accessible to attackers.
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.9.24.2.17.1.1
Apply vendor-supplied patches or upgrade to fixed versions. If immediate patching is not possible, restrict network access to FortiTester management interfaces and implement additional authentication controls.
FortiTester 7.1.1 (or 3.9.2/4.2.1 depending on current branch)
- Identify current FortiTester version using the web UI or CLI
- Access FortiGuard portal at https://www.fortiguard.com/ to obtain the appropriate upgrade image
- Download the fixed version image matching your current branch: 3.9.2 for 3.x, 4.2.1 for 4.x, or 7.1.1 for 7.x
- Access FortiTester administrative interface and navigate to System > Firmware
- Upload the firmware image and initiate the upgrade process
- After reboot, verify the new version is installed and test core functionality
- Verify the login component now properly sanitizes input and does not permit OS command injection
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortitester
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33873 — 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-33873 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