Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io-parser/package.json,/enable-video/node_modules/socket.io-parser/package.json,/inviting-members/node_modules/socket.io-parser/package.json
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.
Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /inviting-members/node_modules/xmlhttprequest-ssl/package.json,/enable-video/node_modules/xmlhttprequest-ssl/package.json,/enable-screen-share/node_modules/xmlhttprequest-ssl/package.json
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.
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io/package.json,/enable-video/node_modules/socket.io/package.json,/inviting-members/node_modules/socket.io/package.json
In socket.io in versions 1.0.0 to 2.3.0 is vulnerable to Cross-Site Websocket Hijacking, it allows an attacker to bypass origin protection using special symbols include "`" and "$".
Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /inviting-members/node_modules/xmlhttprequest-ssl/package.json,/enable-video/node_modules/xmlhttprequest-ssl/package.json,/enable-screen-share/node_modules/xmlhttprequest-ssl/package.json
This affects the package xmlhttprequest before 1.7.0; all versions of package xmlhttprequest-ssl. Provided requests are sent synchronously (async=False on xhr.open), malicious user input flowing into xhr.send could result in arbitrary code being injected and run.
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/engine.io/package.json,/enable-video/node_modules/engine.io/package.json,/inviting-members/node_modules/engine.io/package.json
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io-parser/package.json,/enable-video/node_modules/socket.io-parser/package.json,/inviting-members/node_modules/socket.io-parser/package.json
socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/engine.io/package.json,/enable-video/node_modules/engine.io/package.json,/inviting-members/node_modules/engine.io/package.json
Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the engine.io package, including those who uses depending packages like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
ws is an open source WebSocket client and server library for Node.js. A specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server. The vulnerability has been fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff). In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io/package.json,/enable-video/node_modules/socket.io/package.json,/inviting-members/node_modules/socket.io/package.json
Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io-parser/package.json,/enable-video/node_modules/socket.io-parser/package.json,/inviting-members/node_modules/socket.io-parser/package.json
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.
Details
CVE-2021-31597
### Vulnerable Library - xmlhttprequest-ssl-1.5.5.tgzXMLHttpRequest for Node
Library home page: https://registry.npmjs.org/xmlhttprequest-ssl/-/xmlhttprequest-ssl-1.5.5.tgz
Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /inviting-members/node_modules/xmlhttprequest-ssl/package.json,/enable-video/node_modules/xmlhttprequest-ssl/package.json,/enable-screen-share/node_modules/xmlhttprequest-ssl/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-client-2.2.0.tgz - engine.io-client-3.3.2.tgz - :x: **xmlhttprequest-ssl-1.5.5.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability DetailsThe 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 FixType: 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
WS-2020-0443
### Vulnerable Library - socket.io-2.2.0.tgznode.js realtime framework server
Library home page: https://registry.npmjs.org/socket.io/-/socket.io-2.2.0.tgz
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io/package.json,/enable-video/node_modules/socket.io/package.json,/inviting-members/node_modules/socket.io/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - :x: **socket.io-2.2.0.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability DetailsIn socket.io in versions 1.0.0 to 2.3.0 is vulnerable to Cross-Site Websocket Hijacking, it allows an attacker to bypass origin protection using special symbols include "`" and "$".
Publish Date: 2020-02-20
URL: WS-2020-0443
### CVSS 3 Score Details (8.1)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://hackerone.com/reports/931197
Release Date: 2020-02-20
Fix Resolution: socket.io - 2.4.0
CVE-2020-28502
### Vulnerable Library - xmlhttprequest-ssl-1.5.5.tgzXMLHttpRequest for Node
Library home page: https://registry.npmjs.org/xmlhttprequest-ssl/-/xmlhttprequest-ssl-1.5.5.tgz
Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /inviting-members/node_modules/xmlhttprequest-ssl/package.json,/enable-video/node_modules/xmlhttprequest-ssl/package.json,/enable-screen-share/node_modules/xmlhttprequest-ssl/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-client-2.2.0.tgz - engine.io-client-3.3.2.tgz - :x: **xmlhttprequest-ssl-1.5.5.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability DetailsThis affects the package xmlhttprequest before 1.7.0; all versions of package xmlhttprequest-ssl. Provided requests are sent synchronously (async=False on xhr.open), malicious user input flowing into xhr.send could result in arbitrary code being injected and run.
Publish Date: 2021-03-05
URL: CVE-2020-28502
### CVSS 3 Score Details (8.1)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-h4j5-c7cj-74xg
Release Date: 2021-03-05
Fix Resolution: xmlhttprequest - 1.7.0,xmlhttprequest-ssl - 1.6.2
CVE-2020-36048
### Vulnerable Library - engine.io-3.3.2.tgzThe realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
Library home page: https://registry.npmjs.org/engine.io/-/engine.io-3.3.2.tgz
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/engine.io/package.json,/enable-video/node_modules/engine.io/package.json,/inviting-members/node_modules/engine.io/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-2.2.0.tgz - :x: **engine.io-3.3.2.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability DetailsEngine.IO before 4.0.0 allows attackers to cause a denial of service (resource consumption) via a POST request to the long polling transport.
Publish Date: 2021-01-08
URL: CVE-2020-36048
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36048
Release Date: 2021-01-08
Fix Resolution: engine.io - 4.0.0
CVE-2020-36049
### Vulnerable Library - socket.io-parser-3.3.0.tgzsocket.io protocol parser
Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.3.0.tgz
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io-parser/package.json,/enable-video/node_modules/socket.io-parser/package.json,/inviting-members/node_modules/socket.io-parser/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-client-2.2.0.tgz - :x: **socket.io-parser-3.3.0.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability Detailssocket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.
Publish Date: 2021-01-08
URL: CVE-2020-36049
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-xfhh-g9f5-x4m4
Release Date: 2021-01-08
Fix Resolution: socket.io-parser - 3.3.2,3.4.1
CVE-2022-41940
### Vulnerable Library - engine.io-3.3.2.tgzThe realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
Library home page: https://registry.npmjs.org/engine.io/-/engine.io-3.3.2.tgz
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/engine.io/package.json,/enable-video/node_modules/engine.io/package.json,/inviting-members/node_modules/engine.io/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-2.2.0.tgz - :x: **engine.io-3.3.2.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability DetailsEngine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the engine.io package, including those who uses depending packages like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
Publish Date: 2022-11-22
URL: CVE-2022-41940
### CVSS 3 Score Details (6.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/socketio/engine.io/security/advisories/GHSA-r7qp-cfhv-p84w
Release Date: 2022-11-22
Fix Resolution: engine.io - 3.6.1,6.2.1
CVE-2021-32640
### Vulnerable Libraries - ws-6.1.4.tgz, ws-6.1.3.tgz### ws-6.1.4.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-6.1.4.tgz
Path to dependency file: /inviting-members/package.json
Path to vulnerable library: /inviting-members/node_modules/ws/package.json,/enable-video/node_modules/ws/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-client-2.2.0.tgz - engine.io-client-3.3.2.tgz - :x: **ws-6.1.4.tgz** (Vulnerable Library) ### ws-6.1.3.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-6.1.3.tgz
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/ws/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-client-2.2.0.tgz - engine.io-client-3.3.2.tgz - :x: **ws-6.1.3.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability Detailsws is an open source WebSocket client and server library for Node.js. A specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server. The vulnerability has been fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff). In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.
Publish Date: 2021-05-25
URL: CVE-2021-32640
### CVSS 3 Score Details (5.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/websockets/ws/security/advisories/GHSA-6fc8-4gx4-v693
Release Date: 2021-05-25
Fix Resolution: 5.2.3,6.2.2,7.4.6
CVE-2020-28481
### Vulnerable Library - socket.io-2.2.0.tgznode.js realtime framework server
Library home page: https://registry.npmjs.org/socket.io/-/socket.io-2.2.0.tgz
Path to dependency file: /enable-screen-share/package.json
Path to vulnerable library: /enable-screen-share/node_modules/socket.io/package.json,/enable-video/node_modules/socket.io/package.json,/inviting-members/node_modules/socket.io/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - :x: **socket.io-2.2.0.tgz** (Vulnerable Library)
Found in HEAD commit: e9e491a76eb5cd18d7ae16768f36b599bd0d9d08
Found in base branch: main
### Vulnerability DetailsThe package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.
Publish Date: 2021-01-19
URL: CVE-2020-28481
### CVSS 3 Score Details (4.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481
Release Date: 2021-01-19
Fix Resolution: 2.4.0