Perry < 0.5.1166 JWT Expiration Bypass via verify_decode
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| PerryTS | perry | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Perryts | Perry |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.357% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Perryts
Perryts perry |
|
| Vendors & Products |
Perryts
Perryts perry |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Perry before 0.5.1166 contains a JWT validation vulnerability that allows remote attackers to bypass token expiration by exploiting the unconditional setting of validate_exp = false in the verify_decode helper within the stdlib JWT verification path. Attackers in possession of a previously issued bearer token can present expired tokens to any jwt.verify() call and retain authenticated access indefinitely, bypassing force-expired sessions such as user logout or administrative revocation. | |
| Title | Perry < 0.5.1166 JWT Expiration Bypass via verify_decode | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV3_1
|