Security Fix for Cross-site Scripting (XSS) - huntr.dev #263
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
[FIX] XSS using htmlentities()
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.
https://huntr.dev/users/Mik317 has fixed the Cross-site Scripting (XSS) vulnerability 馃敤. Mik317 has been awarded $25 for fixing the vulnerability through the huntr bug bounty program 馃挼. Think you could fix a vulnerability like this?
Get involved at https://huntr.dev/
Q | A
Version Affected | ALL
Bug Fix | YES
Original Pull Request | 418sec#2
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/packagist/instagram-php-api/1/README.md
User Comments:
馃搳 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-packagist-instagram-php-api
鈿欙笍 Description *
An
XSSissue occured in theinstagram-php-apiproject, which was due toinsecure reflectionofusersuppliedinput through the?error_descriptionparameter.馃捇 Technical Description *
I used the
htmlentities()method to sanitize themalicious parameter, avoiding the issue aforementioned.馃悰 Proof of Concept (PoC) *
No POC, but the issue was clear by the code
馃敟 Proof of Fix (PoF) *
No POC, but
htmlentities()works fine with every scenario馃憤 User Acceptance Testing (UAT)
Just used
htmlentities()on astring