MFA Fuzzing and Json.Unmarshal Panic fix #30854
Merged
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.
This expands the coverage of fuzzing in
lib/web/fuzz_test.go
and includes adding seeds. From this work a new panic was discovered where a pointer is allocated then a pointer to the pointer is passed intojson.Unmarshal
. It is then possible for this original pointer to remain anil
reference.This pattern looks unexpected, so all cases of double pointers being passed into
json.Unmarshal
were changed to the more standard empty struct pointer style to avoid potential nil reference panics.Originally opened in this PR: https://github.com/gravitational/teleport-private/pull/891 but severity was deemed low enough to fix directly in OSS
Backporting will be done through release PR's already open: