strapi@3.0.0-alpha.17 vulnerabilities
An open source headless CMS solution to create and manage your own API. It provides a powerful dashboard and features to make your life easier. Databases supported: MongoDB, MySQL, MariaDB, PostgreSQL, SQLite
-
latest version
3.6.11
-
first published
11 years ago
-
latest version published
2 years ago
-
licenses detected
- >=1.0.0 <3.1.0-alpha.4
Direct Vulnerabilities
Known vulnerabilities in the strapi package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) through the How to fix Server-Side Request Forgery (SSRF)? There is no fixed version for |
*
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Improper Input Validation due to mishandling hidden attributes within admin API responses. Exploiting this vulnerability allows users with permission to read user data in the settings section to read all users' data, including password hashes, by manipulating columns when using the filter function. How to fix Improper Input Validation? Upgrade |
<3.6.10
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via file upload module, which allows attackers with How to fix Cross-site Scripting (XSS)? There is no fixed version for |
*
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to insufficient sanitization of user-supplied data in the file Note:
Users of How to fix Cross-site Scripting (XSS)? There is no fixed version for |
*
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Information Exposure by allowing an authenticated user with access to the admin panel to view private and sensitive data, such as email and password reset tokens via API responses. There are many scenarios in which such details from API users can leak in the JSON response within the admin panel, either through a direct or indirect relationship. Access to this information enables a user to compromise these users’ accounts if the password reset API endpoints have been enabled. In a worst-case scenario, a low-privileged user could get access to a high-privileged API account 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. Note: Versions 4.0.0 up to 4.1.9 are also vulnerable, however, they're available only through the Github repository. Upgrade to version 4.1.10 to fix this vulnerability. How to fix Information Exposure? Upgrade |
<3.6.10
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Information Exposure by allowing an authenticated user with access to the admin panel to 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. 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. How to fix Information Exposure? Upgrade |
<3.6.10
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Information Exposure due to the storage of passwords in a recoverable format in the How to fix Information Exposure? Upgrade |
<3.6.9
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Improper Authentication. If an attacker is able to access a valid admin session, they can then change the account's password without being required to input the current password. How to fix Improper Authentication? A fix was pushed into the |
*
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF). How to fix Server-side Request Forgery (SSRF)? Upgrade |
<3.2.5
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Access Restriction Bypass. A remote authenticated attacker is allowed to bypass security restrictions because templates are stored in a global variable without any sanitation. By sending a specially crafted request, an attacker could exploit this vulnerability to update the email template for both password reset and account confirmation emails. How to fix Access Restriction Bypass? Upgrade |
<3.0.2
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Denial of Service (DoS). The sanitisation regex in How to fix Denial of Service (DoS)? Upgrade |
<3.0.0-beta.18.4
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Arbitrary Code Injection. The package fails to sanitize plugin names in the How to fix Arbitrary Code Injection? Upgrade |
<3.0.0-beta.17.8
|
strapi is a HTTP layer sits on top of Koa. Affected versions of this package are vulnerable to Improper Access Control. It mishandles password resets within How to fix Improper Access Control? Upgrade |
<3.0.0-beta.17.5
|