dbcve.org
Tableau ServerApplication · Tableau

CVE-2022-22127

HIGH · 7.2 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to after 2021.4.4 or later.
See remediation →
78/100
Remediation priority · High
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
Tableau is aware of a broken access control vulnerability present in Tableau Server affecting Tableau Server customers using Local Identity Store for managing users. The vulnerability allows a malicious site administrator to change passwords for users in different sites hosted on the same Tableau Server, resulting in the potential for unauthorized access to data.Tableau Server versions affected are:2020.4.16, 2021.1.13, 2021.2.10, 2021.3.9, 2021.4.4 and earlierNote: All future releases of Tableau Server will address this security issue. Versions that are no longer supported are not tested and may be vulnerable.

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

Broken access control vulnerability in Tableau Server with Local Identity Store allows a malicious site administrator to change passwords for users in different sites on the same server, enabling unauthorized access to data across site boundaries.

MitigationUpgrade Tableau Server to a version beyond 2021.4.4 (or the latest patched release) to address this 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
Tableau ServerApplication
Affected:>= 2020.4, <= 2020.4.16>= 2021.1, <= 2021.1.13>= 2021.2, <= 2021.2.10>= 2021.3, <= 2021.3.9>= 2021.4, <= 2021.4.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Determine installed Tableau Server version
    Run 'tsm version' from the command line or check the Tableau Server About page in the administration interface
    Affected if The version falls within any of these ranges: 2020.4.0-2020.4.16, 2021.1.0-2021.1.13, 2021.2.0-2021.2.10, 2021.3.0-2021.3.9, or 2021.4.0-2021.4.4
  2. Identify the identity store type in use
    Examine the Tableau Server identity store configuration file (typically at /var/opt/tableau/tableau_server/data/tabsvc/config/identityStore.xml or via 'tsm configuration get' for the 'wgserver.authentication.identities.store' setting)
    Affected if The identity store is configured as 'local' (not using Active Directory, LDAP, or other external identity providers)
  3. Determine if multiple sites exist on the server
    Query the Tableau Server REST API endpoint '/api/api-version/sites' or view the Sites page in the Tableau Server administration interface to count the number of sites
    Affected if More than one site is configured on the server

A server is affected if it runs a vulnerable version of Tableau Server (2020.4.0-2020.4.16, 2021.1.0-2021.1.13, 2021.2.0-2021.2.10, 2021.3.0-2021.3.9, or 2021.4.0-2021.4.4) AND uses Local Identity Store AND has multiple sites 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 2021.4.4
Interim mitigation

Upgrade Tableau Server to a version beyond 2021.4.4 (or the latest patched release) to address this vulnerability.

Recommended fix High confidence

Upgrade to 2021.4.5 or later (or the latest patch in your respective version branch: 2020.4.17, 2021.1.14, 2021.2.11, or 2021.3.10)

  1. 1. Identify the current Tableau Server version by navigating to Server Status Page or running 'tsm version' command
  2. 2. Based on your current version branch, upgrade to the next available patch release that addresses the vulnerability
  3. 3. For 2020.4.x users: upgrade to 2020.4.17 or later
  4. 4. For 2021.1.x users: upgrade to 2021.1.14 or later
  5. 5. For 2021.2.x users: upgrade to 2021.2.11 or later
  6. 6. For 2021.3.x users: upgrade to 2021.3.10 or later
  7. 7. For 2021.4.x users: upgrade to 2021.4.5 or later
  8. 8. Run 'tsm maintenance validate' after upgrade to ensure integrity
Caveat Review Tableau Server release notes for breaking changes between versions; major version upgrades may have compatibility considerations with existing workbooks and integrations

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

Fix this in Tableau Server 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-22127 — 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-22127 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