Skip to content

Dashboard subscription settings interface reveals list of recipients to sandboxed users

Moderate
nemanjaglumac published GHSA-492f-qxr3-9rrv Jan 27, 2023

Package

No package listed

Affected versions

<x43.7.1, <x.44.6.1, <x45.2.1

Patched versions

0.43.7.1, 1.43.7.1, 0.44.6.1, 1.44.6.1, 0.45.2.1, 1.45.2.1

Description

Impact

Sandboxed users shouldn't be able to view data about other Metabase users anywhere in the Metabase application. However, when a sandbox user viewed the settings for a dashboard subscription, and another user had added users to that subscription, the sandboxed user would be able to view the list of recipients for that subscription.

Patches

This issue will be patched in 0.43.7.1, 1.43.7.1, 0.44.6.1, 1.44.6.1, 0.45.2.1, 1.45.2.1. When a sandboxed user views the list of recipients for a dashboard subscriptions, they will only ever see their user account in the list of recipients.

Workarounds

There are no workarounds for this issue aside from upgrading.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

CVE ID

CVE-2023-23628

Weaknesses

No CWEs