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

Backport of Add input validation to getRuleInfo to prevent panic into release/1.10.x #14735

Merged
merged 2 commits into from
Mar 28, 2022

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #14501 to be assessed for backporting due to the inclusion of the label backport/1.10.x.

The below text is copied from the body of the original PR.


A panic can be caused if input to the ParsePolicy function contains a field whose value is an empty slice. This is due to a lack of length check in the underlying getRuleInfo function which assumes the parsed slice to contain at least one value. The panic can be prevented by returning an error from getRuleInfo if an empty slice is encountered.

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/vault-4014/duly-driving-lark branch 4 times, most recently from 2bb2685 to aec52d4 Compare March 28, 2022 15:06
@vercel vercel bot temporarily deployed to Preview – vault March 28, 2022 15:06 Inactive
@ccapurso ccapurso merged commit 878dffa into release/1.10.x Mar 28, 2022
@ccapurso ccapurso deleted the backport/vault-4014/duly-driving-lark branch March 28, 2022 15:51
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

Successfully merging this pull request may close these issues.

3 participants