Remove _openAPIToGraphQL from arbitrary JSON in arrays #450
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cwisdo
changed the title
Signed-off-by: Christopher <[email protected]>
cwisdo
force-pushed
the
fix-nested-openAPIToGraphQL-exposure
branch
from
aadb016
to
b594dc8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I observed this leak in a mutation that returned an array of arbitrary JSON objects representing rows of data (attribute-value pairs). In addition to leaking the security information, it increased the data size significantly as every JSON object at the second level contained the data.