9
2
Fork
You've already forked platform
2

Concurrent sessions allowed across devices with no notification or revocation #140

Open
opened 2026年04月02日 21:51:06 +02:00 by xenushka · 1 comment

Summary
Multiple simultaneous sessions are permitted from different Qubes/devices with no notification or visibility to the user.

Steps to Reproduce

  1. Register and log in via dashboard on dev qube
  2. Log in with the same passkey on distrust qube
  3. Both sessions remain active concurrently

Expected Behavior
At minimum, the user should be notified of a new session from a new device. Ideally, users should be able to view and revoke active sessions.

Actual Behavior
Both sessions are silently active with no indication to the user.

Security Impact
If a session cookie is compromised, an attacker can maintain a parallel session indefinitely with no signal to the legitimate user. This is inconsistent with the trust model of the platform.

Suggested Fix (pick one or more)

  • Enforce single-session: new login invalidates all prior sessions
  • Add a session management UI showing active devices with revoke option
  • Send email notification when a new session is initiated from a new device

Verified via
Two separate browser sessions on two different machines, both authenticated simultaneously.

**Summary** Multiple simultaneous sessions are permitted from different Qubes/devices with no notification or visibility to the user. **Steps to Reproduce** 1. Register and log in via dashboard on dev qube 2. Log in with the same passkey on distrust qube 3. Both sessions remain active concurrently **Expected Behavior** At minimum, the user should be notified of a new session from a new device. Ideally, users should be able to view and revoke active sessions. **Actual Behavior** Both sessions are silently active with no indication to the user. **Security Impact** If a session cookie is compromised, an attacker can maintain a parallel session indefinitely with no signal to the legitimate user. This is inconsistent with the trust model of the platform. **Suggested Fix (pick one or more)** - Enforce single-session: new login invalidates all prior sessions - Add a session management UI showing active devices with revoke option - Send email notification when a new session is initiated from a new device **Verified via** Two separate browser sessions on two different machines, both authenticated simultaneously.

Enforce single-session: new login invalidates all prior sessions

This is super annoying if anyone's on the dashboard while also doing things on the CLI, and every time I find an application that does this, it tends to bother me.

Add a session management UI showing active devices with revoke option

This definitely seems like a good idea.

Send email notification when a new session is initiated from a new device

Also a good idea, but what are we considering "new"? Do we fingerprint clients and go based on that? That could be some GDPR or California privacy regulation wonkiness.

> Enforce single-session: new login invalidates all prior sessions This is super annoying if anyone's on the dashboard while also doing things on the CLI, and every time I find an application that does this, it tends to bother me. >Add a session management UI showing active devices with revoke option This definitely seems like a good idea. > Send email notification when a new session is initiated from a new device Also a good idea, but what are we considering "new"? Do we fingerprint clients and go based on that? That could be some GDPR or California privacy regulation wonkiness.
Sign in to join this conversation.
No Branch/Tag specified
main
feat/paddle-byoc-subscriptions
feat/legal-publish-doc
fix/issue-116-duplicate-ssh-key
fix/issue-307-remove-apps
fix/issue-265-http-port-private
fix/issue-330-remove-build-binary
feat/issue-164-account-id
fix/issue-119-logout-confirmation
feat/add-tofu-lockfile-cache
feat/webauthn-discoverable-login
docs/issue-339-install-instructions
fix/issue-336-split-qr-login-tokens
fix/verify-app-source-preflight
fix/many-git-push-deploy
fix/issue-334-email-verification-throttle
fix/issue-273-billing-url
fix/issue-333-final-usage-collection
fix/issue-270-low-credit-email
fix/issue-301-remove-auto-topup
fix/issue-320-byoc-auth-first
fix/issue-348-git-progress-checklist
fix/issue-321-byoc-caution-hcl
fix/issue-332-resource-id-suspension
fix/eif-app-mode-normalization
feat/cli-stagex-container
fix/eif-s3-layer-cache
fix/authz-role-checks
fix/paddle-customdata-credit-mint
fix/cli-hangs-unsupported-ssh-url
feat/print-platform-commit-dashboard
anton/feat/multi-user
fix/config-domain-validation
anton/support-ssh-destroy-get
fix/cli-config-dir
feat/publish-build-inputs
feat/locksmith-polishing
fix/procfile-run-command-no-split
anton/byoc-require-login
fix/hcl-init-template
feat/egress-default-deny
ryansquared/hcl
quotas
anton/feat/region-routing-resource-unavailable-alert
fix/attestation-502-dashboard
ryansquared/systemdize
fix/verify-git-credential-hang
anton/fix-low-credits-alert
xenushka/rename-byoc
ryansquared/add-download-eif
add-debug-flag
test/pr1-integration-harness
anton/fix/only-pass-required-env-vars
ryansquared/add-database-bucket
No results found.
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Component/Enclave-Builder
This issue affects Enclave Builder (git-push and CLI)
Component/Infrastructure
This issue affects generic Caution hosted infra components
Deploy/BYOC
Relates to Caution Bring-your-own-compute
Deploy/Full-managed
Relates to Caution fully managed cloud
Deploy/Self-hosted
Relates to Caution deployed on self-hosted infra
Interface/API
This issue affects the API
Interface/CLI
This issue affects the command line interface
Interface/Git
This issue affects the Git `push` interface
Interface/Web
This issue affects the web dashboard
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
caution/platform#140
Reference in a new issue
caution/platform
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?