dbcve.org
FortiadcApplication · Fortinet

CVE-2022-33875

HIGH · 8.8 CVSS v3.1 Published 2022-12-06
Fix available
A fix is available. Upgrade to after 6.2.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 improper neutralization of special elements used in an SQL Command ('SQL Injection') vulnerability in Fortinet FortiADC version 7.1.0, version 7.0.0 through 7.0.2 and version 6.2.4 and below allows an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP 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 confidence

SQL injection vulnerability in Fortinet FortiADC's web interface allows authenticated attackers to inject malicious SQL commands via specially crafted HTTP requests, potentially enabling arbitrary code or command execution on the affected device.

MitigationUpgrade FortiADC to a patched version beyond 7.1.0, 7.0.2, or 6.2.4. Apply the latest Fortinet security patches for the product line.

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
FortiadcApplication
Affected:>= 5.2.0, <= 6.2.4= 7.0.0= 7.0.1= 7.0.2= 7.1.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FortiADC web interface is accessible
    Check if the FortiADC web UI ports (HTTP port 80, HTTPS port 443) are listening. From a management station, attempt to reach https://<fortiadc-ip>/ or check with command: ssh admin@<fortiadc-ip> 'get system interface' to list interface configurations with web UI enabled.
    Affected if The web interface (HTTP/HTTPS) is enabled and reachable on the FortiADC device.
  2. Identify installed FortiADC version
    Access the FortiADC CLI via console or SSH and run: 'get system status' or 'diagnose sys version'. The version number will be displayed in the output.
    Affected if The installed version is 5.2.0 through 6.2.4 inclusive, or exactly 7.0.0, 7.0.1, 7.0.2, or 7.1.0.
  3. Verify web UI service status
    In FortiADC CLI, run: 'get system global | grep -i admin' or 'show system admin' to confirm the web UI administrative service is enabled. The web UI must be active for the SQL injection to be exploitable.
    Affected if The web UI administrative service is enabled (typically on port 443 for HTTPS).
  4. Check for existing administrative users
    In FortiADC CLI, run: 'show system admin' to list configured administrative accounts. The SQL injection requires an authenticated attacker, so accounts must exist.
    Affected if There is at least one administrative user account configured with access to the web interface.

You are affected if FortiADC is running a version in the range 5.2.0 to 6.2.4 or exactly 7.0.0-7.1.0 AND the web interface is enabled with at least one administrative user configured.

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.2.4
Interim mitigation

Upgrade FortiADC to a patched version beyond 7.1.0, 7.0.2, or 6.2.4. Apply the latest Fortinet security patches for the product line.

Recommended fix Moderate confidence

FortiADC 6.2.5 or later for 6.x branch; FortiADC 7.0.3 or later for 7.0.x branch; FortiADC 7.1.1 or later for 7.1.x branch (or latest 7.x stable release)

  1. 1. Identify the currently installed FortiADC version using the Web UI (System > Dashboard > Status) or CLI: get system status
  2. 2. Determine the appropriate upgrade path based on your current major version
  3. 3. Download the corresponding fixed firmware from Fortinet Customer Support portal (https://support.fortinet.com/)
  4. 4. Upload the firmware file via FortiADC Web UI (System > Firmware) or CLI: execute firmware upgrade
  5. 5. After upgrade, verify the version change and confirm the SQL injection vulnerability is resolved
  6. 6. Test that normal FortiADC operations (load balancing, SSL inspection, etc.) function correctly
Caveat Review Fortinet release notes for your target version to check for configuration or behavioral changes between your current and new version, as some legacy features may be deprecated

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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