@strapi/plugin-users-permissions@4.5.5 vulnerabilities
Protect your API with a full-authentication process based on JWT
latest version
5.6.0
latest non vulnerable version
first published
3 years ago
latest version published
12 days ago
licenses detected
- >=0
Direct Vulnerabilities
Known vulnerabilities in the @strapi/plugin-users-permissions package. This does not include vulnerabilities belonging to this package’s dependencies.
How to fix?
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
@strapi/plugin-users-permissions is a headless CMS Affected versions of this package are vulnerable to Replay Attack due to sending session tokens as URL query parameters and using instead an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method. An attacker can use the SSO token and get a JWT token to be able to interact with the various API routes. Notes: This is a competition advisory for CVE-2024-34065 How to fix Replay Attack? Upgrade | <4.24.2 |
@strapi/plugin-users-permissions is a headless CMS Affected versions of this package are vulnerable to Open Redirect when user-controllable data is incorporated into the target of a redirection in an unsafe way. In this specific context, this vulnerability allows the SSO token to be stolen, allowing an attacker to authenticate himself within the application. Notes: If parameter $_GET["callback"] is defined in the GET request, the assignment does not evaluate all conditions, but stops at the beginning. The value is then stored in the cookie koa.sess:
Which once base64 decoded become The signature of the cookie is stored in cookie How to fix Open Redirect? Upgrade | <4.24.2 |
@strapi/plugin-users-permissions is a headless CMS Affected versions of this package are vulnerable to Improper Access Control via the "User Registration" API due to improper sanitization of custom fields. An attacker can gain unauthorized access to private fields during user registration by sending a post request with content to fill the private fields. How to fix Improper Access Control? Upgrade | >=4.0.0 <4.13.1 |
@strapi/plugin-users-permissions is a headless CMS Affected versions of this package are vulnerable to Denial of Service (DoS) such that an attacker can circumvent the rate limit on the login function of Strapi's admin screen. How to fix Denial of Service (DoS)? Upgrade | <4.12.1 |
@strapi/plugin-users-permissions is a headless CMS Affected versions of this package are vulnerable to Improper Neutralization of Special Elements Used in a Template Engine. Remote attackers can inject a payload into an email template, which can execute code on the server, bypassing validation checks that should prevent code execution. The maintainers report that "This vulnerability’s scope was originally believed to be exploitable only if a malicious actor had access to the Strapi Admin Panel." How to fix Improper Neutralization of Special Elements Used in a Template Engine? Upgrade | >=4.0.0-next.0 <4.5.6 |
@strapi/plugin-users-permissions is a headless CMS Affected versions of this package are vulnerable to Authentication Bypass when using the AWS Cognito login provider's NOTE: After upgrading to the fixed version the AWS Cognito provider must be reconfigured to include the JWKS URL. How to fix Authentication Bypass? Upgrade | >=4.0.0-next.0 <4.6.0 |