apache / apache/kyuubi

[Bug] Session id / operation id are not isolated by share level.

Open
#5,256 11 comments 0 reactions 0 assignees View on GitHub
kind:bug priority:major
Dominant language
Scala
Stars
2.4k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

In USER level and GROUP level anyone can access to other users' / groups' Session and Operation as long as they have the session id or operation id. This breaks the share level isolation and may cause resource leak.

### Affects Version(s)

master

### Kyuubi Server Log Output

_No response_

### Kyuubi Engine Log Output

_No response_

### Kyuubi Server Configurations

```yaml
Disable authentication and authorization.
```

### Kyuubi Engine Configurations

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
- [X] No. I cannot submit a PR at this time.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported access to another user's or group's Session and Operation at USER and GROUP share levels with authentication and authorization disabled. Trace how session and operation IDs are resolved, then verify that cross-share access is denied and cannot cause the reported resource leak.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
backend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.