nerves_hub_web API token theft via CLI login link
nerves-hub nerves_hub_web
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| nerves-hub nerves_hub_web |
| No fix yet |
| nerves-hub nerves_hub_web |
| No fix yet |
| nerves-hub nerves_hub_web |
| No fix yet |
nerves-hub nerves_hub_web
| Product | Affected | Fixed in |
|---|---|---|
| nerves-hub nerves_hub_web |
| No fix yet |
| nerves-hub nerves_hub_web |
| No fix yet |
| nerves-hub nerves_hub_web |
| No fix yet |
Session Fixation vulnerability in the CLI login flow in nerves-hub nerves_hub_web allows an unauthenticated attacker to obtain an API token for another user's account via a crafted login link. Starting a CLI login with POST /api/auth/cli_session needs no authentication and returns a polling token, a confirmation URL that carries that token, and a confirmation code. When a signed-in user opens that URL and clicks Confirm, NervesHub.Accounts.verify_cli_session_token/2 creates an API token for the user's account and stores it on the login, and the next poll of GET /api/auth/cli_session/<token> returns it to whoever started the login.
The confirmation code is only displayed and is never compared with anything, so it cannot show that the person confirming is the one who started the login. The confirm form carries a CSRF token and the page cannot be framed, so the attacker has to persuade the user to open the link and click the button themselves.
This issue affects nerves_hub: from 2.5.0 before 2.5.3.
From the CVE record · EEF
The CLI login flow lets an unauthenticated attacker start a login and send its confirmation link to a signed-in user. If the user opens the link and clicks Confirm, the attacker can poll the login to obtain an API token for that user's account.
Teams running nerves_hub versions 2.5.0 through 2.5.2 should check their deployments.