Lack of JWT Expiration after Log Out in Strapi
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 | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Strapi | Strapi | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4r8w-3jww-m2rp | Strapi is vulnerable to Insufficient Session Expiration |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.695% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Strapi
Strapi strapi |
|
| Vendors & Products |
Strapi
Strapi strapi |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Strapi uses JSON Web Tokens (JWT) for authentication. After logout or account deactivation, the JWT is not invalidated, which allows an attacker who has stolen or intercepted the token to freely reuse it until its expiration date (which is set to 30 days by default, but can be changed). The existence of /admin/renew-token endpoint allows anyone to renew near-expiration tokens indefinitely, further increasing the impact of this attack. This issue has been fixed in version 5.24.1. | |
| Title | Lack of JWT Expiration after Log Out in Strapi | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV4_0
|