chore(deps-dev): [security] bump jquery from 1.12.4 to 3.6.0
Bumps jquery from 1.12.4 to 3.6.0. This update includes security fixes.
Vulnerabilities fixed
Sourced from The Node Security Working Group.
Cross-Site Scripting (XSS) Jquery is a javascript library for DOM traversal and manipulation, event handling, animation, and Ajax.
When text/javascript responses are received from cross-origin ajax requests not containing the option
dataType, the result is executed injQuery.globalEvalpotentially allowing an attacker to execute arbitrary code on the origin.Affected versions: >=1.4.0 =1.12.3 <=2.2.4
Sourced from The GitHub Security Advisory Database.
Potential XSS vulnerability in jQuery
Impact
Passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e.
.html(),.append(), and others) may execute untrusted code.Patches
This problem is patched in jQuery 3.5.0.
Workarounds
To workaround the issue without upgrading, adding the following to your code:
jQuery.htmlPrefilter = function( html ) { return html; };You need to use at least jQuery 1.12/2.2 or newer to be able to apply this workaround.
References
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/ https://jquery.com/upgrade-guide/3.5/
... (truncated)
Affected versions: >= 1.2 < 3.5.0
Sourced from The GitHub Security Advisory Database.
Potential XSS vulnerability in jQuery In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.
This problem is patched in jQuery 3.5.0.
Affected versions: >= 1.0.3 < 3.5.0
Sourced from The GitHub Security Advisory Database.
Moderate severity vulnerability that affects jquery jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
Affected versions: < 3.0.0
Sourced from The GitHub Security Advisory Database.
Moderate severity vulnerability that affects jquery A prototype pollution vulnerability exists in jQuery versions < 3.4.0 that allows an attacker to inject properties on Object.prototype.
Affected versions: < 3.4.0
Sourced from The GitHub Security Advisory Database.
Moderate severity vulnerability that affects jquery jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable proto property, it could extend the native Object.prototype.
Affected versions: < 3.4.0
Release notes
Sourced from jquery's releases.
jQuery 3.5.0 Released!
See the blog post: https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/ and the upgrade guide: https://jquery.com/upgrade-guide/3.5/
NOTE: Despite being a minor release, this update includes a breaking change that we had to make to fix a security issue (
CVE-2020-11022). Please follow the blog post & the upgrade guide for more details.
Commits
0cc1ad63.6.0aed59daRelease: remove the need to install grunt globally8606ce4Release: update version to 3.6.0-pre8b50fbeRelease: drop the need for npm as a local dependencya21a4b2Release: upgrade release dependenciesc208debRelease: update AUTHORS.txt1654874Selector: Update Sizzle from 2.3.5 to 2.3.6f8bdb12Support: ensure display is set to block for the support div (#4844)627c573Build: Rename master to main across the repository15b62a2Deferred: Rename master to primary- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language -
@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)