dbcve.org
FortiproxyApplication · Fortinet

CVE-2022-42476

HIGH · 8.2 CVSS v3.1 Published 2023-03-07
Fix available
A fix is available. Upgrade to after 7.2.3 or later.
See remediation →
84/100
Remediation priority · High
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
A relative path traversal vulnerability [CWE-23] in Fortinet FortiOS version 7.2.0 through 7.2.2, 7.0.0 through 7.0.8 and before 6.4.11, FortiProxy version 7.2.0 through 7.2.2 and 7.0.0 through 7.0.8 allows privileged VDOM administrators to escalate their privileges to super admin of the box via crafted CLI 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 · moderate confidence

A relative path traversal vulnerability (CWE-23) in FortiOS 7.2.0-7.2.2, 7.0.0-7.0.8, and before 6.4.11, as well as FortiProxy 7.2.0-7.2.2 and 7.0.0-7.0.8, allows privileged VDOM administrators to escalate their privileges to super admin through crafted CLI requests.

MitigationUpgrade FortiOS and FortiProxy to patched versions beyond the vulnerable releases (7.2.3+, 7.0.9+, 6.4.11+) to remediate this path traversal privilege escalation vulnerability.

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.1.0, <= 1.1.6>= 1.2.0, <= 1.2.13>= 2.0.0, <= 2.0.11>= 7.0.0, <= 7.0.7= 7.2.0= 7.2.1
FortiosOperating system
Affected:>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.8>= 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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. Identify FortiOS version
    Run 'get system status' or 'fortios -v' via CLI to retrieve the installed FortiOS version
    Affected if Version is 6.2.0-6.2.12, 6.4.0-6.4.11, 7.0.0-7.0.8, or 7.2.0-7.2.3
  2. Identify FortiProxy version
    Run 'get system status' via CLI to retrieve the installed FortiProxy version
    Affected if Version is 1.1.0-1.1.6, 1.2.0-1.2.13, 2.0.0-2.0.11, 7.0.0-7.0.7, 7.2.0, or 7.2.1
  3. Check if VDOM is enabled
    Run 'get system vdom' or 'show system vdom' via CLI to verify if Virtual Domains are configured
    Affected if VDOM is enabled and multiple VDOM administrators exist with elevated privileges
  4. Review VDOM administrator privileges
    Run 'get system admin' and inspect admin accounts with 'set vdom' entries showing access to non-root VDOMs
    Affected if Multiple privileged VDOM administrator accounts exist alongside super_admin users

Environment is affected if running a vulnerable FortiOS (6.2.0-6.2.12, 6.4.0-6.4.11, 7.0.0-7.0.8, 7.2.0-7.2.3) or FortiProxy (1.1.0-1.1.6, 1.2.0-1.2.13, 2.0.0-2.0.11, 7.0.0-7.0.7, 7.2.0-7.2.1) version with VDOMs and privileged VDOM administrators 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 7.2.3
Interim mitigation

Upgrade FortiOS and FortiProxy to patched versions beyond the vulnerable releases (7.2.3+, 7.0.9+, 6.4.11+) to remediate this path traversal privilege escalation vulnerability.

Recommended fix High confidence

FortiOS: 7.2.4+, 7.0.9+, 6.4.12+ | FortiProxy: 7.2.3+, 7.0.9+, 2.0.12+, 1.2.14+, 1.1.7+

  1. 1. Identify the currently installed FortiOS or FortiProxy version using the CLI command: get system status
  2. 2. For FortiOS 7.2.x deployments, upgrade to FortiOS 7.2.4 or later
  3. 3. For FortiOS 7.0.x deployments, upgrade to FortiOS 7.0.9 or later
  4. 4. For FortiOS 6.4.x deployments, upgrade to FortiOS 6.4.12 or later
  5. 5. For FortiProxy 7.2.x deployments, upgrade to FortiProxy 7.2.3 or later
  6. 6. For FortiProxy 7.0.x deployments, upgrade to FortiProxy 7.0.9 or later
  7. 7. For FortiProxy 2.0.x deployments, upgrade to FortiProxy 2.0.12 or later
  8. 8. For FortiProxy 1.2.x deployments, upgrade to FortiProxy 1.2.14 or later
Caveat Review Fortinet release notes for potential configuration or feature changes between versions before upgrading

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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