In most cases, trust boundaries are violated when a secret is exposed in a source code repository or an uncontrolled deployment environment.
Unintended people who don’t need to know the secret might get access to it. They might then be able to use it to gain unwanted access to associated
services or resources.
The trust issue can be more or less severe depending on the people’s role and entitlement.
What is the potential impact?
Tableau secrets scopes depend on the type of secret. From the most impactful to the least:
- Account passwords
- Personal access tokens (PAT)
- "Credentials token", received after a SignIn request
Their scopes vary in terms of lifetime, access, and privileges.
Below are some real-world scenarios that illustrate some impacts of an attacker exploiting the secret.
Compromise of sensitive data
If the affected service is used to store or process personally identifiable information or other sensitive data, attackers knowing an
authentication secret could be able to access it. Depending on the type of data that is compromised, it could lead to privacy violations, identity
theft, financial loss, or other negative outcomes.
In most cases, a company suffering a sensitive data compromise will face a reputational loss when the security issue is publicly disclosed.
Data visualization corruption and takeover
With control over the Tableau application, the attacker can modify dashboards, alter data sources, or inject malicious code. This can result in the
manipulation of displayed data, misleading visualizations, or even the introduction of backdoors for further exploitation.
The attacker may even attempt to escalate their privileges within the Tableau environment. By gaining administrative access or higher-level
permissions, they can perform more significant actions, such as modifying access controls, adding or deleting users, or changing system
configurations.
