Strapi: Password Reset Does Not Revoke Existing Refresh Sessions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| strapi | strapi | affected |
|
||||||
| strapi | @strapi/admin | affected |
|
||||||
| strapi | @strapi/plugin-users-permissions | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Strapi | Admin |
|
||||||||
| Strapi | Plugin-users-permissions |
|
||||||||
| Strapi | Strapi |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hvp3-26wx-g2w4 | Strapi: Password Reset Does Not Revoke Existing Refresh Sessions |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.341% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Strapi admin
Strapi plugin-users-permissions |
|
| Vendors & Products |
Strapi admin
Strapi plugin-users-permissions |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Strapi
Strapi strapi |
|
| CPEs | cpe:2.3:a:strapi:strapi:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Strapi
Strapi strapi |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied `deviceId`. When a password change or reset request did not include a `deviceId`, no refresh tokens were revoked, leaving every prior session active. An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing persistent unauthorized access for the lifetime of the refresh token (up to 30 days by default). Rotating credentials no longer terminated an active attacker session, defeating password reset as a containment measure. The patch in version 5.33.3 invalidates all refresh tokens associated with the user on every password change and password reset, regardless of whether a `deviceId` is supplied. A new device-scoped session is then issued to the caller as part of the response. | |
| Title | Strapi: Password Reset Does Not Revoke Existing Refresh Sessions | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV4_0
|