Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Prototype-Poisoning.md #4879

Merged
merged 1 commit into from
Jul 4, 2023
Merged

Update Prototype-Poisoning.md #4879

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/Guides/Prototype-Poisoning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,7 @@

But first, if we use a JavaScript framework to process incoming JSON data, take
a moment to read up on [Prototype Poisoning](https://medium.com/intrinsic/javascript-prototype-poisoning-vulnerabilities-in-the-wild-7bc15347c96)
in general, and the specific [technical details]
(https://github.com/hapijs/hapi/issues/3916) of this issue.
in general, and the specific [technical details](https://github.com/hapijs/hapi/issues/3916) of this issue.

Check failure on line 16 in docs/Guides/Prototype-Poisoning.md

View workflow job for this annotation

GitHub Actions / Lint Markdown 

Line length [Expected: 80; Actual: 107]
This could be a critical issue so, we might need to verify your own code first.
It focuses on specific framework however, any solution that uses `JSON.parse()`
to process external data is potentially at risk.
Expand Down