jquery-form/form

Fortify SCA: Code Injection .

Open

#554 opened on Aug 3, 2018

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (5,209 stars) (2,199 forks)batch import
help wantedneed more info

Description

Please review Instructions for Reporting a Bug.

Description:

I have no idea about whether it has been fixed in later versions. but the code scan is not passed.

Expected Behavior:

Actual behavior:

Source: jquery.form.js:812 Read xhr.responseXML() 810 var ct = xhr.getResponseHeader('content-type') || '', 811 xml = type === 'xml' || !type && ct.indexOf('xml') >= 0, 812 data = xml ? xhr.responseXML : xhr.responseText; 813 814 if (xml && data.documentElement.nodeName === 'parsererror') { Sink: jquery.form.js:781 setTimeout() 779 780 // clean up 781 setTimeout(function() { 782 if (!s.iframeTarget) { 783 $io.remove();

Versions:

jqform:3.51

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
JavaScriptjQueryweb securityFortify SCA
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the code injection vulnerability reported at lines 812 and 781 of jquery.form.js. Check the comments for any additional context. Determine if the responseXML usage could lead to code injection and propose a safe handling approach. Review the repository's security guidelines and any existing security patches.
Fortify SCA: Code Injection . · jquery-form/form#554 | Good First Issue