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

Security - Document Assumption of Single Tenancy #28

Open
jlewi opened this issue May 18, 2023 · 0 comments
Open

Security - Document Assumption of Single Tenancy #28

jlewi opened this issue May 18, 2023 · 0 comments

Comments

@jlewi
Copy link
Owner

jlewi commented May 18, 2023

Each instance of hydros should be considered single tenant.
We don't have sufficient security guarantees in place to prevent a user of hydros to escalating their permissions to be those of hydros. So anyone who can use hydros e.g. by submitting to a repository hydros has access to should be considered to at least have viewer permission on all repositories to which an instance of hydros has access.

For example, we don't ensure that the repository/person who created a ManifestSync has access to the repositories mentioned in the ManifestSync. So suppose we have the following 3 repositories on which an instance of hydros is installed
RepoA
RepoB
RepoC
So hydros has access to all three.
Now suppose we check into RepoA a ManifestSync that hydrates from RepoB to RepoC.
Then in principle someone with access to RepoA & RepoC but not RepoB could use hydros to exfiltrate code to RepoC.

We should update the documentation to make this clear

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant