A delete session for one object reveals the rest of a private container

Aperta
#4,301 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

Start by tracing how the node validates owner-signed session tokens for header and search requests, using the reproduction steps to compare those checks with payload downloads and deletes. The issue names no source files or tests, so locate the request handlers and authorization tests for these operations. Done means the token permits deleting only its named object and does not allow reading another object's header or listing container objects.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug I4 neofs-storage S4 security U2

The owner granted permission to delete a single object. That same token lets the recipient list every object in the container and read the header of any of them. On a private container those reads are otherwise forbidden.

Expected Behavior

The token authorizes deletion of the one object it names. Header reads and searches of any other object are denied.

Current Behavior

With that token, a header request for a different object succeeds, and a search returns every object in the container. Downloading another object's payload is still denied. Deleting another object does not complete: the node answers that the session token was not found. The standard command-line client refuses to send a header or search request with a delete token, so this shows up only when a client attaches the token the owner signed and sends it unchanged.

Steps to Reproduce (for bugs)

  1. Create a private container and store two objects in it.
  2. As the owner, issue a session for another account. Limit it to the first object and to the delete operation, and sign it with the owner key.
  3. From the other account, without the token, request the header of the second object. The request is denied.
  4. Repeat that header request with the token attached as issued. The header is returned.
  5. Search the container with the same token. Both objects are listed.
Lingua principale
Go
Stelle
37
Fork
56
Merge medio
1g 21h
PR unite (30g)
46

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nspcc-dev/neofs-node

Tutte le issue di nspcc-dev/neofs-node

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.