dbcve.org
FortianalyzerApplication · Fortinet

CVE-2022-42477

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 7.0.7 or later.
See remediation →
57/100
Remediation priority · Elevated
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 input validation vulnerability [CWE-20] in FortiAnalyzer version 7.2.1 and below, version 7.0.6 and below, 6.4 all versions may allow an authenticated attacker to disclose file system information via custom dataset SQL queries.

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

FortiAnalyzer versions 7.2.1 and below, 7.0.6 and below, and 6.4 all versions contain an improper input validation vulnerability (CWE-20) in the custom dataset SQL query feature. An authenticated attacker can craft malicious SQL queries to disclose file system information, exploiting insufficient validation of user-supplied input in custom dataset definitions.

MitigationUpgrade FortiAnalyzer to a patched version (7.2.2 or later for the 7.2 branch, 7.0.7 or later for the 7.0 branch). Alternatively, restrict access to the custom dataset feature to only trusted administrators and implement additional input validation controls.

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
FortianalyzerApplication
Affected:>= 6.4.0, < 7.0.7= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 FortiAnalyzer version
    Run 'get system status' via CLI or check System Settings > Settings in the web UI to retrieve the installed version number
    Affected if The version is 6.4.x any build, 7.0.x through 7.0.6, or 7.2.0 through 7.2.1
  2. Locate the custom dataset feature
    In the web UI, navigate to Reports > Report Definitions > Custom Datasets, or use the CLI command 'diagnose dlp dataset list' to see custom dataset configurations
    Affected if Custom dataset definitions exist in the system, indicating the feature is in use
  3. Verify access to custom dataset creation
    Check user/administrator account privileges in System > Administrators or via 'get system admin' CLI command to see which roles can create or edit custom datasets
    Affected if Any administrator account with Report Designer or equivalent privileges can access custom dataset configuration, making the feature exploitable
  4. Review recent custom dataset SQL definitions
    Inspect existing custom dataset queries via the web UI or CLI 'diagnose dlp dataset list' to see if any contain suspicious SQL statements accessing filesystem tables or functions
    Affected if Custom datasets contain SQL queries that reference filesystem access functions or non-standard tables not typical of normal reporting

A user is affected if their FortiAnalyzer version falls within 6.4.x, 7.0.x through 7.0.6, or 7.2.0-7.2.1 AND the custom dataset feature is accessible to authenticated administrators.

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

Upgrade FortiAnalyzer to a patched version (7.2.2 or later for the 7.2 branch, 7.0.7 or later for the 7.0 branch). Alternatively, restrict access to the custom dataset feature to only trusted administrators and implement additional input validation controls.

Recommended fix High confidence

FortiAnalyzer 7.0.7 or later, or 7.2.2 or later

  1. Identify the currently installed FortiAnalyzer version using the web UI or CLI command: 'get system status'
  2. For FortiAnalyzer 6.4.x versions: upgrade to FortiAnalyzer 7.0.7 or later, or 7.2.2 or later
  3. For FortiAnalyzer 7.0.x versions (up to 7.0.6): upgrade to FortiAnalyzer 7.0.7 or later, or 7.2.2 or later
  4. For FortiAnalyzer 7.2.0: upgrade to FortiAnalyzer 7.2.2 or later
  5. Verify the upgrade was successful and the version matches the target fixed release
  6. After upgrade, validate that custom dataset SQL queries no longer allow unauthorized file system information disclosure
Caveat Review FortiAnalyzer release notes for the target version to check for any configuration or feature changes that may affect your deployment

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

Fix this in Fortianalyzer 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-42477 — 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-42477 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