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
Due to improper type validation in attachment parsing the Socket.io js library, it is possible to overwrite the _placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object.
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.
ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
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
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
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors.
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: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/debug/package.json,/enable-video/node_modules/debug/package.json,/enable-audio/node_modules/debug/package.json,/inviting-members/node_modules/debug/package.json,/utilizing-events/node_modules/debug/package.json,/enable-screen-share/node_modules/debug/package.json
The debug module is vulnerable to regular expression denial of service when untrusted user input is passed into the o formatter. It takes around 50k characters to block for 2 seconds making this a low severity issue.
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
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2022-2421
### 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 base branch: main
### Vulnerability DetailsDue to improper type validation in attachment parsing the Socket.io js library, it is possible to overwrite the _placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object.
Publish Date: 2022-10-26
URL: CVE-2022-2421
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### CVSS 3 Score Details (9.8)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: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-qm95-pgcg-qqfq
Release Date: 2022-10-26
Fix Resolution (socket.io-parser): 3.3.3
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### 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
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS:
### 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
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 3.0%
### 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-ssl): 1.6.1
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2024-37890
### Vulnerable Libraries - ws-6.1.3.tgz, ws-6.1.4.tgz### 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) ### 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)
Found in base branch: main
### Vulnerability Detailsws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
Publish Date: 2024-06-17
URL: CVE-2024-37890
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.0%
### 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/websockets/ws/security/advisories/GHSA-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution (ws): 6.2.3
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
Fix Resolution (ws): 6.2.3
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### 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
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### 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): 3.6.0
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2024-38355
### 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 base branch: main
### Vulnerability DetailsSocket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors.
Publish Date: 2024-06-19
URL: CVE-2024-38355
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.0%
### CVSS 3 Score Details (7.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/socketio/socket.io/security/advisories/GHSA-25hc-qcg6-38wj
Release Date: 2024-06-19
Fix Resolution (socket.io): 4.6.2
Direct dependency fix Resolution (nexmo-client): 8.7.2
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.1%
### 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
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### 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 (ws): 6.2.2
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
Fix Resolution (ws): 6.2.2
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
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 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
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.2%
### 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 (socket.io): 2.4.0
Direct dependency fix Resolution (nexmo-client): 4.0.1-ot
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2017-16137
### Vulnerable Library - debug-4.1.1.tgzsmall debugging utility
Library home page: https://registry.npmjs.org/debug/-/debug-4.1.1.tgz
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/debug/package.json,/enable-video/node_modules/debug/package.json,/enable-audio/node_modules/debug/package.json,/inviting-members/node_modules/debug/package.json,/utilizing-events/node_modules/debug/package.json,/enable-screen-share/node_modules/debug/package.json
Dependency Hierarchy: - nexmo-client-4.0.0.tgz (Root Library) - socket.io-2.2.0.tgz - :x: **debug-4.1.1.tgz** (Vulnerable Library)
Found in base branch: main
### Vulnerability DetailsThe debug module is vulnerable to regular expression denial of service when untrusted user input is passed into the o formatter. It takes around 50k characters to block for 2 seconds making this a low severity issue.
Publish Date: 2018-06-07
URL: CVE-2017-16137
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.3%
### CVSS 3 Score Details (3.7)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - 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/advisories/GHSA-gxpj-cx7g-858c
Release Date: 2018-04-26
Fix Resolution (debug): 4.3.1
Direct dependency fix Resolution (nexmo-client): 8.7.2
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.