Fix panic caused by parsing json.Number
values for TypeCommaStringSlice fields
#14522
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.
Vault will panic when it attempts to parse fields with a schema of TypeCommaStringSlice if the provided value is an integer specifically if provided within the JSON body of an HTTP request. The underlying cause is within the
ParseCommaStringSlice
function ingo-secure-stdlib/parseutil
. The issue has been fixed ingo-secure-stdlib
#29.The changes introduced within this PR are:
v0.1.4
ofgo-secure-stdlib/parseutil
json.Number
inputBefore fix:
Panic in server logs (truncated):
After fix: