dbcve.org
FortiproxyApplication · Fortinet

CVE-2022-45861

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-07
Fix available
A fix is available. Upgrade to after 7.2.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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 access of uninitialized pointer vulnerability [CWE-824] in the SSL VPN portal of Fortinet FortiOS version 7.2.0 through 7.2.3, version 7.0.0 through 7.0.9 and before 6.4.11 and FortiProxy version 7.2.0 through 7.2.1, version 7.0.0 through 7.0.7 and before 2.0.11 allows a remote authenticated attacker to crash the sslvpn daemon via an HTTP GET request.

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

An uninitialized pointer vulnerability (CWE-824) in the SSL VPN portal of FortiOS and FortiProxy allows an authenticated remote attacker to crash the sslvpn daemon via a specially crafted HTTP GET request, causing denial of service.

MitigationUpgrade FortiOS to version 7.2.4 or later, 7.0.10 or later, 6.4.11 or later; upgrade FortiProxy to version 7.2.2 or later, 7.0.8 or later, or 2.0.11 or later. Alternatively, disable SSL VPN portal access if not needed.

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
FortiproxyApplication
Affected:>= 1.2.0, <= 1.2.13>= 2.0.0, <= 2.0.11>= 7.0.0, <= 7.0.7= 1.1.5= 1.1.6= 7.2.0= 7.2.1
FortiosOperating system
Affected:>= 6.2.0, <= 6.2.13>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.9>= 7.2.0, <= 7.2.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify the product and version
    Run 'get system status' on the FortiGate or FortiProxy CLI to display the firmware version and model information
    Affected if The displayed version falls within the affected ranges: FortiOS 6.2.0-6.2.13, 6.4.0-6.4.11, 7.0.0-7.0.9, or 7.2.0-7.2.3; FortiProxy 1.2.0-1.2.13, 2.0.0-2.0.11, 7.0.0-7.0.7, 1.1.5, 1.1.6, 7.2.0, or 7.2.1
  2. Confirm SSL VPN portal is enabled
    Run 'get vpn ssl settings' in the CLI to check if SSL VPN is configured and active
    Affected if SSL VPN is enabled (status shows 'enable' or the portal is configured with active users/groups)
  3. Verify remote authentication is permitted
    Run 'get vpn ssl settings' and check the 'auth-type' or 'Authentication' settings to determine if remote user authentication is allowed
    Affected if Remote authentication is permitted for SSL VPN, meaning the attacker can authenticate to exploit the vulnerability

You are affected if your device runs FortiOS or FortiProxy within the listed version ranges AND SSL VPN portal is enabled and accessible to authenticated remote 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 7.2.3
Interim mitigation

Upgrade FortiOS to version 7.2.4 or later, 7.0.10 or later, 6.4.11 or later; upgrade FortiProxy to version 7.2.2 or later, 7.0.8 or later, or 2.0.11 or later. Alternatively, disable SSL VPN portal access if not needed.

Recommended fix High confidence

FortiOS: 6.4.12+, 7.0.10+, 7.2.4+ | FortiProxy: 2.0.12+, 7.0.8+, 7.2.2+

  1. 1. Identify the currently installed FortiOS or FortiProxy version using 'get system status' CLI command.
  2. 2. For FortiOS 6.2.x: Upgrade to version 6.4.12 or later (recommended: 6.4.12).
  3. 3. For FortiOS 6.4.x: Upgrade to version 6.4.12 or later (recommended: 6.4.12).
  4. 4. For FortiOS 7.0.x: Upgrade to version 7.0.10 or later (recommended: 7.0.10).
  5. 5. For FortiOS 7.2.x: Upgrade to version 7.2.4 or later (recommended: 7.2.4).
  6. 6. For FortiProxy 1.1.5 and 1.2.x: Upgrade to version 2.0.12 or later (recommended: 2.0.12).
  7. 7. For FortiProxy 2.0.x: Upgrade to version 2.0.12 or later (recommended: 2.0.12).
  8. 8. For FortiProxy 7.0.x: Upgrade to version 7.0.8 or later (recommended: 7.0.8).
Caveat Major version upgrades (e.g., 6.x to 7.x) may introduce configuration or feature changes; review release notes before upgrading

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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