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.

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

Already on GitHub? Sign in to your account

Security Fix for Cross-site Scripting (XSS) - huntr.dev #1164

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

huntr-helper
Copy link

https://huntr.dev/users/mufeedvh has fixed the Cross-site Scripting (XSS) vulnerability 馃敤. mufeedvh 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#1
GitHub Issue | #1130
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/npm/x-editable/1/README.md

User Comments:

馃搳 Metadata *

Bounty URL: https://www.huntr.dev/bounties/1-npm-x-editable

鈿欙笍 Description *

The project x-editable validated JSON string with poorly crafted Regex making it easy to bypass the validation and inject JavaScript code to achieve XSS (Cross-site Scripting).

馃捇 Technical Description *

The implemented Regex to validate JSON was so poor that it only checks whether if the string begins and ends with [ or { and their counterparts ] or }. This means you can give it a string such as []+alert(1)+[] and it will match.

Come on man why would you write a whole Regex to validate JSON semantics lol, and JavaScript's Regex match doesn't have certain expressions implemented making it even harder.

So how do we fix it? Just parse the JSON with the JavaScript function JSON.parse() and if it fails, it's not a valid JSON string.

馃悰 Proof of Concept (PoC) *

Refer: #1130

Payload used to bypass the current validation:

[]+alert(1)+[]

馃敟 Proof of Fix (PoF) *

Parse the input JSON string and if it fails, it wouldn't proceed dynamically adding it to the HTML code preventing the XSS (Cross-site Scripting) vulnerability.

if (typeof s === 'string' && s.length) {
    try {
        JSON.parse(s);
        if (safe) {
            try {
                /*jslint evil: true*/
                s = (new Function('return ' + s))();
                /*jslint evil: false*/
            } catch (e) {} finally {
                return s;
            }
        } else {
            /*jslint evil: true*/
            s = (new Function('return ' + s))();
            /*jslint evil: false*/
        }
        return s;
    } catch (e) {
        // pass
    }
}

馃憤 User Acceptance Testing (UAT)

Just added a try/catch block to check for JSON.parse() fails.

@JamieSlome
Copy link

@vitalets - let me know if you have any questions or thoughts?

Cheers! 馃嵃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants