CYBER CODE RED

Get real-time updates on Telegram

ghsa:GHSA-Q84F-53JG-9PPM: better-auth >= 1.3.8-beta.3, < 1.7.0-rc.3

better-auth: Device login approval does not show the requesting client or permissions. Affected range: >= 1.3.8-beta.3, < 1.7.0-rc.3. Fixed version: 1.7.0-rc.3.

Affected technology

better-auth · >= 1.3.8-beta.3, < 1.7.0-rc.3
Vendor not specified by the source

Component: Not specified by the source

Attack conditions (Source advisory, CVSS 3.1): Network (remote) · No privileges required · User interaction required

What an attacker can do

The source says you are affected only if all of these are also true: - An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client. - Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests. - Users may approve a code or complete verification link they did not start and cannot compare with a device they have. - Your application accepts the session token that the device flow returns, for example through the bearer plugin. Source advisory’s CVSS 3.1 assessment rates confidentiality and integrity impact as high; availability impact as none.

Published

Product
better-auth
KEV
no

Provenance

Stable permalink: https://cybercodered.org/item/adv-ghsa-ghsa-q84f-53jg-9ppm.html