CVE-2021-31597 (High) detected in xmlhttprequest-ssl-1.5.5.tgz - autoclosed

[mend-for-github-com[bot]]

CVE-2021-31597 - High Severity Vulnerability

Vulnerable Library - xmlhttprequest-ssl-1.5.5.tgz

XMLHttpRequest for Node

Library home page: https://registry.npmjs.org/xmlhttprequest-ssl/-/xmlhttprequest-ssl-1.5.5.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/karma/node_modules/xmlhttprequest-ssl/package.json

Dependency Hierarchy: - karma-3.1.4.tgz (Root Library) - socket.io-2.1.1.tgz - socket.io-client-2.1.1.tgz - engine.io-client-3.2.1.tgz - :x: **xmlhttprequest-ssl-1.5.5.tgz** (Vulnerable Library)

Found in HEAD commit: dce0d0698ddf3d5a57eec238050dbad494da4a5e

Vulnerability Details

The xmlhttprequest-ssl package before 1.6.1 for Node.js disables SSL certificate validation by default, because rejectUnauthorized (when the property exists but is undefined) is considered to be false within the https.request function of Node.js. In other words, no certificate is ever rejected.

Publish Date: 2021-04-23

URL: CVE-2021-31597

CVSS 3 Score Details (9.4)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31597

Release Date: 2021-04-23

Fix Resolution: xmlhttprequest-ssl - 1.6.1

[mend-for-github-com[bot]]

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #230

[mend-for-github-com[bot]]

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #230

[mend-for-github-com[bot]]

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #230