e54b52ec03
In previous implementation of `neofs-node` app object session was not checked for substitution of the object related to it. Also, for access checks, the session object was substituted instead of the one from the request. This, on the one hand, made it possible to inherit the session from the parent object for authorization for certain actions. On the other hand, it covered the mentioned object substitution, which is a critical vulnerability. Next changes are applied to processing of all Object service requests: - check if object session relates to the requested object - use requested object in access checks. Disclosed problem of object context inheritance will be solved within Signed-off-by: Leonard Lyubich <ctulhurider@gmail.com> |
||
|---|---|---|
| .. | ||
| acl | ||
| delete | ||
| get | ||
| head | ||
| internal | ||
| put | ||
| search | ||
| util | ||
| metrics.go | ||
| response.go | ||
| server.go | ||
| sign.go | ||
| transport_splitter.go | ||