dbcve.org
FortisoarApplication · Fortinet

CVE-2022-29062

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 7.0.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
Multiple relative path traversal vulnerabilities [CWE-23] in Fortinet FortiSOAR before 7.2.1 allows an authenticated attacker to write to the underlying filesystem with nginx permissions via 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

FortiSOAR before version 7.2.1 contains multiple path traversal vulnerabilities (CWE-23) that allow authenticated attackers to write files to arbitrary locations on the filesystem via crafted HTTP requests containing '../' sequences. The attack succeeds with nginx user permissions, limiting the scope of writable locations.

MitigationUpgrade FortiSOAR to version 7.2.1 or later. If immediate patching is not possible, implement strict input validation on all file path parameters to reject sequences containing directory traversal characters and restrict nginx user permissions to minimal necessary directories.

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
FortisoarApplication
Affected:>= 7.0.0, < 7.0.3= 7.2.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 installed FortiSOAR version
    Check the FortiSOAR UI under System Administration > Settings > About, or use the command line: 'csadm --info' or check version file in the FortiSOAR installation directory
    Affected if The version displayed is 7.0.0 through 7.0.2, or exactly 7.2.0
  2. Confirm version is in affected range
    Compare your installed version against the affected ranges: 7.0.0 <= version < 7.0.3 OR version == 7.2.0
    Affected if Your installed version falls within 7.0.0-7.0.2 or is exactly 7.2.0
  3. Verify nginx user access controls
    Check the nginx configuration file (typically /etc/nginx/nginx.conf or within /etc/nginx/conf.d/) and review the user directive. Also verify file permissions on directories that nginx can write to
    Affected if The nginx user has write access to sensitive system directories beyond the intended FortiSOAR data directories
  4. Audit for unexpected file creations
    Review web server logs for any requests containing '../' sequences in path parameters. Check for new files in system directories (/tmp, /var, /etc) that were created around the time of suspicious activity
    Affected if Log analysis reveals requests with '../' traversal sequences or unexpected files appear in system directories outside FortiSOAR's intended data paths

You are affected if your FortiSOAR installation is version 7.0.0-7.0.2 or exactly 7.2.0 and the nginx user has write access beyond intended application directories.

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 7.0.3 or later
Fixed in 7.0.3
Interim mitigation

Upgrade FortiSOAR to version 7.2.1 or later. If immediate patching is not possible, implement strict input validation on all file path parameters to reject sequences containing directory traversal characters and restrict nginx user permissions to minimal necessary directories.

Recommended fix High confidence

FortiSOAR 7.2.1 or later

  1. 1. Identify the current FortiSOAR version by navigating to the FortiSOAR UI and checking the system information, or by running the appropriate CLI command.
  2. 2. Create a complete backup of the FortiSOAR database and configuration following Fortinet's documented backup procedures.
  3. 3. Download FortiSOAR version 7.2.1 or later from the Fortinet Support Portal (https://support.fortinet.com).
  4. 4. Schedule a maintenance window as upgrades may require system downtime.
  5. 5. Apply the upgrade by following Fortinet's official FortiSOAR upgrade guide, typically involving accessing the FortiSOAR administration interface and importing the upgrade package.
  6. 6. After the upgrade completes, verify the new version by checking the system information in the FortiSOAR UI.
  7. 7. Validate that the path traversal vulnerability is resolved by confirming the fix is applied and testing that relative path traversal attempts are properly sanitized/blocked.
Caveat Standard security upgrade; review Fortinet release notes for any minor configuration or compatibility notes between versions

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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