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.

Sign up for GitHub

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

Jump to bottom

rust-spiffe: make sure that the claims returned by the validation operation are as expected #290

Closed
hug-dev opened this issue Nov 26, 2020 · 1 comment
Closed

rust-spiffe: make sure that the claims returned by the validation operation are as expected #290

hug-dev opened this issue Nov 26, 2020 · 1 comment
Labels
multitenancy Getting Parsec to provide isolated key stores for multiple clients based on an identity mechanism security Issues related to the security and privacy of the service small Effort label

Comments

@hug-dev
Copy link
Member

hug-dev commented Nov 26, 2020

This is an issue for the rust-spiffe repository when the JWT-SVID feature is merged in.

The ValidateJWTSVID operation returns the claims of the JWT-SVID. The validation function should make sure that those are the same than the one contained in the JWT-SVID being validated.

Because the Workload API endpoint is currently trusted, an attacker could return the SPIFFE ID that they want and then access all possible keys.

#289 would fix this as well.
@hug-dev hug-dev added security Issues related to the security and privacy of the service multitenancy Getting Parsec to provide isolated key stores for multiple clients based on an identity mechanism labels Nov 26, 2020
@ionut-arm ionut-arm added the small Effort label label Feb 3, 2021
@hug-dev
Copy link
Member Author

hug-dev commented Jun 22, 2021

Opened here

@hug-dev hug-dev closed this as completed Jun 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
multitenancy Getting Parsec to provide isolated key stores for multiple clients based on an identity mechanism security Issues related to the security and privacy of the service small Effort label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hug-dev @ionut-arm