CVE-2020-11022 (Medium) detected in jquery-1.11.1.min.js, jquery-2.1.4.min.js - autoclosed

[mend-bolt-for-github]

CVE-2020-11022 - Medium Severity Vulnerability

Vulnerable Libraries - jquery-1.11.1.min.js, jquery-2.1.4.min.js

jquery-1.11.1.min.js

JavaScript library for DOM operations

Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js

Path to dependency file: /node_modules/chroma-js/docs/index.html

Path to vulnerable library: /node_modules/chroma-js/docs/libs/jquery/jquery-1.11.1.min.js

Dependency Hierarchy:

• ❌ jquery-1.11.1.min.js (Vulnerable Library)

jquery-2.1.4.min.js

JavaScript library for DOM operations

Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js

Path to dependency file: /node_modules/chroma-js/test/html/cubehelix.html

Path to vulnerable library: /node_modules/chroma-js/test/html/cubehelix.html

Dependency Hierarchy:

• ❌ jquery-2.1.4.min.js (Vulnerable Library)

Found in HEAD commit: 6b6da833aa3bd0bc4a04b5931212e0ecf31d7235

Found in base branch: master

Vulnerability Details

In jQuery versions greater than or equal to 1.2 and before 3.5.0, 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. This problem is patched in jQuery 3.5.0.

Publish Date: 2020-04-29

URL: CVE-2020-11022

CVSS 3 Score Details (6.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/

Release Date: 2020-04-29

Fix Resolution: jQuery - 3.5.0

---

Step up your Open Source Security Game with WhiteSource here

[mend-bolt-for-github]

✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.