Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replay attack on queries can leak confidential information #1604

Open
brenzi opened this issue Jul 1, 2024 · 0 comments
Open

replay attack on queries can leak confidential information #1604

brenzi opened this issue Jul 1, 2024 · 0 comments
Labels
F1-security possible vulnerability

Comments

@brenzi
Copy link
Collaborator

brenzi commented Jul 1, 2024

currently, TrustedGetters have no nonce, therefore they can be replayed.

This is not critical in general as the signed payload is transmitted via TLS directly into the enclave and can't be intercepted by a MITM. But in presence of browser-required reverse proxy (because of declined self-signed certs or for load balancing) for relaying requests in web apps, this may allow the operator of the reverse proxy to leak confidential information.

options to look into:

  • For convenience when polling balances, we may not want to use a per-request nonce, but rather a timestamp until which the query shall be valid. then the user can select more or less security with longer or shorter expiry
  • return a session token for subsequent authentications? doesn't really add security
@brenzi brenzi added the F1-security possible vulnerability label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F1-security possible vulnerability
Projects
None yet
Development

No branches or pull requests

1 participant