[GHSA-9c47-m6qq-7p4h] Prototype Pollution in JSON5 via Parse Method #1540
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.
Updates
Comments
json5/json5#298 (comment)
Ah, I think I fat-fingered this and submitted before it was finished. It seems I cannot edit this PR anymore either 😬
Anyway, what I was trying to do was report that it was also fixed in the v1 line (
json5@1.0.2
), as noted here:So what I would suggest is that the vulnerability have two versions entries:
Similar to this
xmldom
vulnerability: