You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /utilizing-events/node_modules/socket.io/package.json,/enable-audio/node_modules/socket.io/package.json,/simple-conversation/node_modules/socket.io/package.json
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/socket.io-client/node_modules/socket.io-parser/package.json,/enable-audio/node_modules/socket.io-client/node_modules/socket.io-parser/package.json,/utilizing-events/node_modules/socket.io-client/node_modules/socket.io-parser/package.json
Path to dependency file: /enable-audio/package.json
Path to vulnerable library: /enable-audio/node_modules/socket.io-parser/package.json,/simple-conversation/node_modules/socket.io-parser/package.json,/utilizing-events/node_modules/socket.io-parser/package.json
Dependency Hierarchy:
nexmo-client-4.1.0.tgz (Root Library)
socket.io-2.5.0.tgz
❌ socket.io-parser-3.4.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
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: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/ws/package.json,/enable-audio/node_modules/ws/package.json,/utilizing-events/node_modules/ws/package.json
Dependency Hierarchy:
nexmo-client-4.1.0.tgz (Root Library)
socket.io-client-2.5.0.tgz
engine.io-client-3.5.3.tgz
❌ ws-7.4.6.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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: /utilizing-events/package.json
Path to vulnerable library: /utilizing-events/node_modules/socket.io/package.json,/enable-audio/node_modules/socket.io/package.json,/simple-conversation/node_modules/socket.io/package.json
Dependency Hierarchy:
nexmo-client-4.1.0.tgz (Root Library)
❌ socket.io-2.5.0.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
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 [email protected] (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-audio/package.json
Path to vulnerable library: /enable-audio/node_modules/socket.io-parser/package.json,/simple-conversation/node_modules/socket.io-parser/package.json,/utilizing-events/node_modules/socket.io-parser/package.json
Dependency Hierarchy:
nexmo-client-4.1.0.tgz (Root Library)
socket.io-2.5.0.tgz
❌ socket.io-parser-3.4.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
socket.io parser is a socket.io encoder and decoder written in JavaScript complying with version 5 of socket.io-protocol. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. A patch has been released in version 4.2.3.
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/engine.io/package.json,/utilizing-events/node_modules/engine.io/package.json,/enable-audio/node_modules/engine.io/package.json
Dependency Hierarchy:
nexmo-client-4.1.0.tgz (Root Library)
socket.io-2.5.0.tgz
❌ engine.io-3.6.0.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
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.
Path to dependency file: /enable-audio/package.json
Path to vulnerable library: /enable-audio/node_modules/cookie/package.json,/simple-conversation/node_modules/cookie/package.json,/utilizing-events/node_modules/cookie/package.json
Dependency Hierarchy:
nexmo-client-4.1.0.tgz (Root Library)
socket.io-2.5.0.tgz
engine.io-3.6.0.tgz
❌ cookie-0.4.2.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
cookie is a basic HTTP cookie parser and serializer for HTTP servers. The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie. Upgrade to 0.7.0, which updates the validation for name, path, and domain.
mend-for-github.aaakk.us.kgbot
changed the title
nexmo-client-4.1.0.tgz: 3 vulnerabilities (highest severity is: 9.8)
nexmo-client-4.1.0.tgz: 4 vulnerabilities (highest severity is: 9.8)
Jun 19, 2024
mend-for-github.aaakk.us.kgbot
changed the title
nexmo-client-4.1.0.tgz: 4 vulnerabilities (highest severity is: 9.8)
nexmo-client-4.1.0.tgz: 5 vulnerabilities (highest severity is: 9.8)
Jul 24, 2024
mend-for-github.aaakk.us.kgbot
changed the title
nexmo-client-4.1.0.tgz: 5 vulnerabilities (highest severity is: 9.8)
nexmo-client-4.1.0.tgz: 5 vulnerabilities (highest severity is: 10.0)
Sep 8, 2024
mend-for-github.aaakk.us.kgbot
changed the title
nexmo-client-4.1.0.tgz: 5 vulnerabilities (highest severity is: 10.0)
nexmo-client-4.1.0.tgz: 6 vulnerabilities (highest severity is: 10.0)
Oct 18, 2024
Vulnerable Library - nexmo-client-4.1.0.tgz
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /utilizing-events/node_modules/socket.io/package.json,/enable-audio/node_modules/socket.io/package.json,/simple-conversation/node_modules/socket.io/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 Libraries - socket.io-parser-3.3.2.tgz, socket.io-parser-3.4.1.tgz
socket.io-parser-3.3.2.tgz
socket.io protocol parser
Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.3.2.tgz
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/socket.io-client/node_modules/socket.io-parser/package.json,/enable-audio/node_modules/socket.io-client/node_modules/socket.io-parser/package.json,/utilizing-events/node_modules/socket.io-client/node_modules/socket.io-parser/package.json
Dependency Hierarchy:
socket.io-parser-3.4.1.tgz
socket.io protocol parser
Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.4.1.tgz
Path to dependency file: /enable-audio/package.json
Path to vulnerable library: /enable-audio/node_modules/socket.io-parser/package.json,/simple-conversation/node_modules/socket.io-parser/package.json,/utilizing-events/node_modules/socket.io-parser/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
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.
Publish Date: 2022-10-25
URL: CVE-2022-2421
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.2%
CVSS 3 Score Details (10.0)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-qm95-pgcg-qqfq
Release Date: 2022-10-26
Fix Resolution (socket.io-parser): 3.3.3
Direct dependency fix Resolution (nexmo-client): 5.0.0
Fix Resolution (socket.io-parser): 3.3.3
Direct dependency fix Resolution (nexmo-client): 5.0.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-37890
Vulnerable Library - ws-7.4.6.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-7.4.6.tgz
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/ws/package.json,/enable-audio/node_modules/ws/package.json,/utilizing-events/node_modules/ws/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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 Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution (ws): 7.5.10
Direct dependency fix Resolution (nexmo-client): 5.0.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-38355
Vulnerable Library - socket.io-2.5.0.tgz
node.js realtime framework server
Library home page: https://registry.npmjs.org/socket.io/-/socket.io-2.5.0.tgz
Path to dependency file: /utilizing-events/package.json
Path to vulnerable library: /utilizing-events/node_modules/socket.io/package.json,/enable-audio/node_modules/socket.io/package.json,/simple-conversation/node_modules/socket.io/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
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[email protected]
(released in May 2023). The fix was backported in the 2.x branch as well with commitd30630ba10
. 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 Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (7.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: 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
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2023-32695
Vulnerable Library - socket.io-parser-3.4.1.tgz
socket.io protocol parser
Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.4.1.tgz
Path to dependency file: /enable-audio/package.json
Path to vulnerable library: /enable-audio/node_modules/socket.io-parser/package.json,/simple-conversation/node_modules/socket.io-parser/package.json,/utilizing-events/node_modules/socket.io-parser/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
socket.io parser is a socket.io encoder and decoder written in JavaScript complying with version 5 of socket.io-protocol. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. A patch has been released in version 4.2.3.
Publish Date: 2023-05-27
URL: CVE-2023-32695
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.3%
CVSS 3 Score Details (7.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-cqmj-92xf-r6r9
Release Date: 2023-05-27
Fix Resolution (socket.io-parser): 3.4.3
Direct dependency fix Resolution (nexmo-client): 5.0.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2022-41940
Vulnerable Library - engine.io-3.6.0.tgz
The 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.6.0.tgz
Path to dependency file: /simple-conversation/package.json
Path to vulnerable library: /simple-conversation/node_modules/engine.io/package.json,/utilizing-events/node_modules/engine.io/package.json,/enable-audio/node_modules/engine.io/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
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.
Publish Date: 2022-11-22
URL: CVE-2022-41940
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.1%
CVSS 3 Score Details (7.1)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-r7qp-cfhv-p84w
Release Date: 2022-11-22
Fix Resolution (engine.io): 3.6.1
Direct dependency fix Resolution (nexmo-client): 5.0.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-47764
Vulnerable Library - cookie-0.4.2.tgz
HTTP server cookie parsing and serialization
Library home page: https://registry.npmjs.org/cookie/-/cookie-0.4.2.tgz
Path to dependency file: /enable-audio/package.json
Path to vulnerable library: /enable-audio/node_modules/cookie/package.json,/simple-conversation/node_modules/cookie/package.json,/utilizing-events/node_modules/cookie/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
cookie is a basic HTTP cookie parser and serializer for HTTP servers. The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie. Upgrade to 0.7.0, which updates the validation for name, path, and domain.
Publish Date: 2024-10-04
URL: CVE-2024-47764
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-pxg6-pf52-xh8x
Release Date: 2024-10-04
Fix Resolution (cookie): 1.0.1
Direct dependency fix Resolution (nexmo-client): 8.7.2
⛑️ Automatic Remediation will be attempted for this issue.
⛑️Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: