dbcve.org
Tableau ServerApplication · Tableau

CVE-2022-22128

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to after 2022.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Tableau discovered a path traversal vulnerability affecting Tableau Server Administration Agent’s internal file transfer service that could allow remote code execution.Tableau only supports product versions for 24 months after release. Older versions have reached their End of Life and are no longer supported. They are also not assessed for potential security issues and do not receive security updates.

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 path traversal vulnerability in Tableau Server Administration Agent's internal file transfer service allows attackers to use '../' sequences to access files outside the intended directory, potentially enabling remote code execution with the privileges of the file transfer service.

MitigationUpgrade Tableau Server to a supported version (within 24 months of release) that includes the security patch; deprecated EOL versions will not receive fixes.

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
Tableau ServerApplication
Affected:>= 2020.4, <= 2020.4.20>= 2021.1, <= 2021.1.17>= 2021.2, <= 2021.2.15>= 2021.3, <= 2021.3.14>= 2021.4, <= 2021.4.9>= 2022.1, <= 2022.1.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Tableau Server version
    Run 'tsm version' from the Tableau Services Manager command line, or check the version via the Tableau Server UI under 'Server Status' or 'About Tableau Server'
    Affected if The installed version falls within these ranges: 2020.4.0-2020.4.20, 2021.1.0-2021.1.17, 2021.2.0-2021.2.15, 2021.3.0-2021.3.14, 2021.4.0-2021.4.9, or 2022.1.0-2022.1.4
  2. Verify Administration Agent service is enabled
    Check the Tableau Server configuration for the Administration Agent component status via 'tsm status' or the Server UI Diagnostics page
    Affected if The Administration Agent service is running and the internal file transfer service feature is enabled (this is a default component of the Administration Agent in affected versions)
  3. Review file transfer service configuration
    Examine the Administration Agent configuration files for settings related to the internal file transfer service. On Windows check under the Tableau data directory, on Linux check /var/opt/tableau/tableau_server or the configured data directory
    Affected if The internal file transfer service is present and operational in the affected version range, regardless of specific configuration settings

You are affected if Tableau Server is running a version within 2020.4.x through 2022.1.4 AND the Administration Agent's internal file transfer service is enabled (which is default in affected versions).

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 2022.1.4
Interim mitigation

Upgrade Tableau Server to a supported version (within 24 months of release) that includes the security patch; deprecated EOL versions will not receive fixes.

Recommended fix High confidence

Upgrade to 2020.4.21+/2021.1.18+/2021.2.16+/2021.3.15+ or latest 2021.4.x LTS

  1. 1. Identify the current Tableau Server version by navigating to Server Status Page or checking the About dialog
  2. 2. Determine which version branch your current installation belongs to (2020.4.x, 2021.1.x, 2021.2.x, or 2021.3.x)
  3. 3. For 2020.4.x branch: upgrade to version 2020.4.21 or later
  4. 4. For 2021.1.x branch: upgrade to version 2021.1.18 or later
  5. 5. For 2021.2.x branch: upgrade to version 2021.2.16 or later
  6. 6. For 2021.3.x branch: upgrade to version 2021.3.15 or later
  7. 7. Alternatively, upgrade to the latest stable LTS version 2021.4.x which contains the fix for all affected branches
  8. 8. After upgrade, verify the Administration Agent service is running correctly
Caveat Tableau follows a 24-month support window; ensure your target version is still within active support to receive future security updates

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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