Rodauth before 2.47.0 Authentication Bypass via jwt_refresh
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| jeremyevans | rodauth | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Jeremyevans | Rodauth |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.408% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jeremyevans
Jeremyevans rodauth |
|
| Vendors & Products |
Jeremyevans
Jeremyevans rodauth |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Rodauth before 2.47.0 contains an authentication bypass vulnerability in the jwt_refresh route that issues new JWT access tokens without requiring a refresh token. Attackers can present an access token to the refresh route via non-POST methods to obtain a new valid access token, enabling indefinite account access with temporary token possession. | |
| Title | Rodauth before 2.47.0 Authentication Bypass via jwt_refresh | |
| Weaknesses | CWE-613 | |
| References |
|
|
| Metrics |
cvssV3_1
|