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

Abierto
#4,301 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Go
Estrellas
37
Forks
56
Merge medio
1 d 21 h
PR fusionados (30 d)
46

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nspcc-dev/neofs-node

Todos los issues de nspcc-dev/neofs-node

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.