fix stack overflow by limiting the maximum depth of dotted keys #242
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.
What does this change do?
This patch fixes potential stack overflow error in case of huge depths of dotted keys, like
This issue happens during fuzzing testing on google/oss-fuzz platform and prevents the fuzzer from achieving good coverage.
Before the change:
with address sanitizer:
After the change:
Additionally the
-j
option has been added tozip
command infuzzing/build.sh
-- without this option the seed corpus is useless because the fuzzer takes files only from the root level.Is it related to an exisiting bug report or feature request?
No
Pre-merge checklist
origin/master
(if necessary)