CVE Vulnerabilities

CVE-2022-30617

Improper Removal of Sensitive Information Before Storage or Transfer

Published: May 19, 2022 | Modified: Jun 06, 2022
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
9 HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

An authenticated user with access to the Strapi admin panel can view private and sensitive data, such as email and password reset tokens, for other admin panel users that have a relationship (e.g., created by, updated by) with content accessible to the authenticated user. For example, a low-privileged “author” role account can view these details in the JSON response for an “editor” or “super admin” that has updated one of the author’s blog posts. There are also many other scenarios where such details from other users can leak in the JSON response, either through a direct or indirect relationship. Access to this information enables a user to compromise other users’ accounts by successfully invoking the password reset workflow. In a worst-case scenario, a low-privileged user could get access to a “super admin” account with full control over the Strapi instance, and could read and modify any data as well as block access to both the admin panel and API by revoking privileges for all other users.

Weakness

The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.

Affected Software

Name Vendor Start Version End Version
Strapi Strapi 3.0.0 (including) 3.6.10 (excluding)
Strapi Strapi 4.0.0-beta10 (including) 4.0.0-beta10 (including)
Strapi Strapi 4.0.0-beta11 (including) 4.0.0-beta11 (including)
Strapi Strapi 4.0.0-beta12 (including) 4.0.0-beta12 (including)
Strapi Strapi 4.0.0-beta13 (including) 4.0.0-beta13 (including)
Strapi Strapi 4.0.0-beta14 (including) 4.0.0-beta14 (including)
Strapi Strapi 4.0.0-beta15 (including) 4.0.0-beta15 (including)
Strapi Strapi 4.0.0-beta2 (including) 4.0.0-beta2 (including)
Strapi Strapi 4.0.0-beta3 (including) 4.0.0-beta3 (including)
Strapi Strapi 4.0.0-beta4 (including) 4.0.0-beta4 (including)
Strapi Strapi 4.0.0-beta5 (including) 4.0.0-beta5 (including)
Strapi Strapi 4.0.0-beta6 (including) 4.0.0-beta6 (including)
Strapi Strapi 4.0.0-beta7 (including) 4.0.0-beta7 (including)
Strapi Strapi 4.0.0-beta8 (including) 4.0.0-beta8 (including)
Strapi Strapi 4.0.0-beta9 (including) 4.0.0-beta9 (including)

Extended Description

Resources that may contain sensitive data include documents, packets, messages, databases, etc. While this data may be useful to an individual user or small set of users who share the resource, it may need to be removed before the resource can be shared outside of the trusted group. The process of removal is sometimes called cleansing or scrubbing. For example, a product for editing documents might not remove sensitive data such as reviewer comments or the local pathname where the document is stored. Or, a proxy might not remove an internal IP address from headers before making an outgoing request to an Internet site.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References