Vulnerabilities in pkg:npm/@strapi/plugin-content-manager

PACKAGE
Advisory Identifier: GHSA-6j89-frxc-q26m
Advisory Summary

CVE-2024-29181 is a LOW (CVSS 2.3) @strapi/plugin-content-manager leaks data vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting @strapi/plugin content manager libraries in the npm ecosystem. The issue involves @strapi/plugin-content-manager leaks data via relations via the admin panel. Remediation is available by upgrading affected packages to version 4.19.1.

3 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@strapi/plugin-content-manager

3 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@strapi/plugin-content-manager. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-6j89-frxc-q26m CVE-2024-29181 LOW @strapi/plugin-content-manager leaks data via relations via the Admin Panel
GHSA-m284-85mf-cgrc CVE-2023-37263 MODERATE Strapi's field level permissions not being respected in relationship title
GHSA-v8gg-4mq2-88q4 CVE-2023-36472 MODERATE Strapi may leak sensitive user information, user reset password, tokens via content-manager views

CVE-2024-29181 at a Glance

CVE Identifier CVE-2024-29181
GHSA Identifier GHSA-6j89-frxc-q26m
Severity LOW
CVSS v3.1 Base Score 2.3
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product @strapi/plugin content manager
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 2.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N).

Attack Vector Adjacent (AV:A)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-29181

To remediate this vulnerability, upgrade all affected @strapi/plugin content manager dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@strapi/plugin-content-manager fixed: 4.19.1
npm install @strapi/plugin-content-manager@4.19.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @strapi/plugin-content-manager

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2024-29181, inspect your project dependencies using npm:

npm ls @strapi/plugin-content-manager

Analyze the terminal output to locate any version of @strapi/plugin content manager in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.19.1), your application is affected.

Note: The npm ls @strapi/plugin-content-manager command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In @strapi/plugin content manager, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 1. If a super admin creates a collection where an item in the collection has an association to another collection, a user with the Author Role can see the list of associated items they did not create. They should only see their own items that they created, not all items ever created. ### Details At the top level every collection shows blank items for an Author if they did not create the item. This is ideal and works great. However if you associate one private collection to another private collection and an Author creates a new item. The pull down should not show the admins list of previously created items. It should be blank unitl they add their own items. ### PoC 1. Sign in as Admin. Navigate to content creation. 2. Select a collection and verify you have items you created there. And that they have associations to other protected collections. 3. Verify role permissions for your collections are set to CRUD if user created. 4. Log out and sign in as a unrelated Author. 5. Navigate to content management and verify you see collections built by admin but empty for you (as expected) 6. Create a new item as an Author and see the card appear with attributes to fill out. 7. Use the form pull down for the associations. 8. Notice that protected collection items from Admin appear in drop down. These should be hidden ### Impact Security vulnerability where authors have access to protected data created by admin. This could be passwords emails or any other item created for the admin's collection. See images below for more context Permissions set ![image](https://user-images.githubusercontent.com/364910/265132222-66e85726-5e01-4ad3-901a-809270a7f11b.png) Good at top level no items seen ![image](https://user-images.githubusercontent.com/364910/265132292-d63fa6df-f32d-48a3-80d0-48a651c570a8.png) Drop down in Author login can see Admin data ![image](https://user-images.githubusercontent.com/364910/265132393-8105bae2-b45c-4327-b1c6-da093557e64f.png)

CVE-2024-29181 Affected @strapi/plugin content manager Versions

1 component(s)
Fixed Versions:
4.19.1
Product / Package Ecosystem Affected Versions Fixed Version
@strapi/plugin-content-manager
npm
< 4.19.1
4.19.1

References

Frequently Asked Questions

What is CVE-2024-29181?
CVE-2024-29181 is a security vulnerability in @strapi/plugin content manager involving @strapi/plugin-content-manager leaks data via relations via the Admin Panel under CWE-639: Authorization Bypass Through User-Controlled Key.
Which @strapi/plugin content manager versions are affected?
Affected versions include releases prior to 4.19.1 across affected packages: @strapi/plugin-content-manager.
What version fixes CVE-2024-29181?
Upgrading to 4.19.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @strapi/plugin-content-manager affected?
Yes, @strapi/plugin-content-manager is affected in releases prior to 4.19.1. Upgrade your dependency to 4.19.1 or later.
What is the CVSS score of CVE-2024-29181?
CVE-2024-29181 has a CVSS v3.1 base score of 2.3 (LOW) with vector string CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2024-29181?
CVE-2024-29181 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check npm dependencies for CVE-2024-29181?
Run the dependency tree command: 'npm ls @strapi/plugin-content-manager'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6j89-frxc-q26m",
  "modified" : "2024-06-12T19:38:02Z",
  "published" : "2024-06-12T19:38:01Z",
  "aliases" : [ "CVE-2024-29181" ],
  "summary" : "@strapi/plugin-content-manager leaks data via relations via the Admin Panel",
  "details" : "### Summary\n1. If a super admin creates a collection where an item in the collection has an association to another collection, a user with the Author Role can see the list of associated items they did not create. They should only see their own items that they created, not all items ever created.\n\n### Details\nAt the top level every collection shows blank items for an Author if they did not create the item. This is ideal and works great. However if you associate one private collection to another private collection and an Author creates a new item. The pull down should not show the admins list of previously created items. It should be blank unitl they add their own items.\n\n### PoC\n1. Sign in as Admin. Navigate to content creation.\n2. Select a collection and verify you have items you created there. And that they have associations to other protected collections.\n3. Verify role permissions for your collections are set to CRUD if user created.\n4. Log out and sign in as a unrelated Author.\n5. Navigate to content management and verify you see collections built by admin but empty for you (as expected)\n6. Create a new item as an Author and see the card appear with attributes to fill out.\n7. Use the form pull down for the associations.\n8. Notice that protected collection items from Admin appear in drop down. These should be hidden\n\n### Impact\nSecurity vulnerability where authors have access to protected data created by admin. This could be passwords emails or any other item created for the admin's collection. \n\nSee images below for more context\n\nPermissions set\n![image](https://user-images.githubusercontent.com/364910/265132222-66e85726-5e01-4ad3-901a-809270a7f11b.png)\n\nGood at top level no items seen\n![image](https://user-images.githubusercontent.com/364910/265132292-d63fa6df-f32d-48a3-80d0-48a651c570a8.png)\n\nDrop down in Author login can see Admin data\n![image](https://user-images.githubusercontent.com/364910/265132393-8105bae2-b45c-4327-b1c6-da093557e64f.png)\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@strapi/plugin-content-manager"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.19.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/strapi/strapi/security/advisories/GHSA-6j89-frxc-q26m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-29181"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/strapi/strapi/commit/e1dfd4d9f1cab25cf6da3614c1975e4e508e01c6"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/strapi/strapi"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-12T19:38:01Z",
    "nvd_published_at" : "2024-06-12T15:15:50Z"
  }
}