Audiobookshelf: Refresh Token Accepted on Resource Endpoints
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.5%
exploitation probability
0.5%top 62% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
advplyr · audiobookshelfReferences
https://github.com/advplyr/audiobookshelf/commit/8ec547e30289ca61ebc52b13d150e3a2a6c6a752https://github.com/advplyr/audiobookshelf/discussions/4460https://github.com/advplyr/audiobookshelf/pull/5387https://github.com/advplyr/audiobookshelf/releases/tag/v2.36.0https://github.com/advplyr/audiobookshelf/security/advisories/GHSA-798w-wv6c-2c3h