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 considerations for the "test" operation #33

Open
spaceone opened this issue Feb 13, 2024 · 0 comments
Open

Security considerations for the "test" operation #33

spaceone opened this issue Feb 13, 2024 · 0 comments

Comments

@spaceone
Copy link

I don't want to file an erratum but just mention it here. Maybe you want to incorporate this idea into the security considerations.

Often backends have the full data set but restrict writing certain items, so that replaceing a value would not be possible.
But testing for a value would be possible.
Imagine the data structure has some plaintext secrets like {"password: "foobar", …},
then a {"op": "test", "path": "/password", "value": "foobar"} would successfully reveal a matching password, if no restrictions exists for allowed-to-read keys.

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