Backport of fix TypeCommaIntSlice panic caused by json.Number input into release/1.8.x #15081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #15072 to be assessed for backporting due to the inclusion of the label backport/1.8.x.
The below text is copied from the body of the original PR.
Vault will panic when it attempts to parse fields with a schema of
TypeCommaIntSlice
if the provided value is an integer specifically if provided within the JSON body of an HTTP request. This is similar to a recent fix that was implemented forTypeCommaStringSlice
which was fixed in #14522. The issue resides inmapstructure.StringToSliceHookFunc
.The fix provided in this pull request is to check if the raw input is of type
json.Number
and then callingString()
.Fixes #15057