Audiobookshelf: Refresh Token Accepted on Resource Endpoints
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| advplyr | audiobookshelf | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Advplyr | Audiobookshelf |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.465% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Advplyr
Advplyr audiobookshelf |
|
| Vendors & Products |
Advplyr
Advplyr audiobookshelf |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Audiobookshelf is a self-hosted audiobook and podcast server. Prior to 2.36.0, the jwtAuthCheck function in server/auth/TokenManager.js treats JWTs with the refresh token type as bearer access tokens on API and WebSocket resource endpoints such as /api/me instead of restricting them to /auth/refresh, allowing refresh tokens to authenticate as the associated users. This issue is fixed in version 2.36.0. | |
| Title | Audiobookshelf: Refresh Token Accepted on Resource Endpoints | |
| Weaknesses | CWE-287 | |
| References |
|
|
| Metrics |
cvssV4_0
|