Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade socket.io from 4.4.0 to 4.7.4 #270

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade socket.io from 4.4.0 to 4.7.4 #270

wants to merge 1 commit into from

Conversation

NOUIY
Copy link
Owner

@NOUIY NOUIY commented Feb 6, 2024

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade socket.io from 4.4.0 to 4.7.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 15 versions ahead of your current version.
  • The recommended version was released 25 days ago, on 2024-01-12.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Denial of Service (DoS)
SNYK-JS-ENGINEIO-3136336		 589/1000
Why? Has a fix available, CVSS 7.5		 No Known Exploit
Uncaught Exception
SNYK-JS-ENGINEIO-5496331		 589/1000
Why? Has a fix available, CVSS 7.5		 No Known Exploit
Improper Input Validation
SNYK-JS-SOCKETIOPARSER-3091012		 589/1000
Why? Has a fix available, CVSS 7.5		 No Known Exploit
Denial of Service (DoS)
SNYK-JS-SOCKETIOPARSER-5596892		 589/1000
Why? Has a fix available, CVSS 7.5		 No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: socket.io
  • 4.7.4 - 2024-01-12

    Bug Fixes

    • typings: calling io.emit with no arguments incorrectly errored (cb6d2e0), closes #4914

    Links

  • 4.7.3 - 2024-01-03

    Bug Fixes

    • return the first response when broadcasting to a single socket (#4878) (df8e70f)
    • typings: allow to bind to a non-secure Http2Server (#4853) (8c9ebc3)

    Links

  • 4.7.2 - 2023-08-02

    Bug Fixes

    • clean up child namespace when client is rejected in middleware (#4773) (0731c0d)
    • webtransport: properly handle WebTransport-only connections (3468a19)
    • webtransport: add proper framing (a306db0)

    Links

  • 4.7.1 - 2023-06-28

    The client bundle contains a few fixes regarding the WebTransport support.

    Links

  • 4.7.0 - 2023-06-22

    Bug Fixes

    • remove the Partial modifier from the socket.data type (#4740) (e5c62ca)

    Features

    Support for WebTransport

    The Socket.IO server can now use WebTransport as the underlying transport.

    WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

    References:

    Until WebTransport support lands in Node.js, you can use the @ fails-components/webtransport package:

    https://w3c.github.io/webtransport/#custom-certificate-requirements)
    const cert = readFileSync("/path/to/my/cert.pem");
    const key = readFileSync("/path/to/my/key.pem");

    const httpsServer = createServer({
    key,
    cert
    });

    httpsServer.listen(3000);

    const io = new Server(httpsServer, {
    transports: ["polling", "websocket", "webtransport"] // WebTransport is not enabled by default
    });

    const h3Server = new Http3Server({
    port: 3000,
    host: "0.0.0.0",
    secret: "changeit",
    cert,
    privKey: key,
    });

    (async () => {
    const stream = await h3Server.sessionStream("/socket.io/");
    const sessionReader = stream.getReader();

    while (true) {
    const { done, value } = await sessionReader.read();
    if (done) {
    break;
    }
    io.engine.onWebTransportSession(value);
    }
    })();

    h3Server.startServer();">

    import { readFileSync } from "fs";
    
import { createServer } from "https";
    
import { Server } from "socket.io";
    
import { Http3Server } from "@ fails-components/webtransport";
    

    // WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)
    
const cert = readFileSync("/path/to/my/cert.pem");
    
const key = readFileSync("/path/to/my/key.pem");
    

    const httpsServer = createServer({
    
key,
    
cert
    
});
    

    httpsServer.listen(3000);
    

    const io = new Server(httpsServer, {
    
transports: ["polling", "websocket", "webtransport"] // WebTransport is not enabled by default
    
});
    

    const h3Server = new Http3Server({
    
port: 3000,
    
host: "0.0.0.0",
    
secret: "changeit",
    
cert,
    
privKey: key,
    
});
    

    (async () => {
    
const stream = await h3Server.sessionStream("/socket.io/");
    
const sessionReader = stream.getReader();
    

    while (true) {
    
const { done, value } = await sessionReader.read();
    
if (done) {
    
break;
    
}
    
io.engine.onWebTransportSession(value);
    
}
    
})();
    

    h3Server.startServer();

    Added in 123b68c.

    Client bundles with CORS headers

    The bundles will now have the right Access-Control-Allow-xxx headers.

    Added in 63f181c.

    Links

  • 4.6.2 - 2023-05-31

    Bug Fixes

    • exports: move types condition to the top (#4698) (3d44aae)

    Links

  • 4.6.1 - 2023-02-20

    Bug Fixes

    • properly handle manually created dynamic namespaces (0d0a7a2)
    • types: fix nodenext module resolution compatibility (#4625) (d0b22c6)

    Links

  • 4.6.0 - 2023-02-07
    Read more
  • 4.6.0-alpha1 - 2023-01-25

    The RemoteSocket interface, which is returned when the client is
    connected on another Socket.IO server of the cluster, was lacking the
    timeout() method.

    Syntax:

    const sockets = await io.fetchSockets();

    for (const socket of sockets) {
    if (someCondition) {
    socket.timeout(1000).emit("some-event", (err) => {
    if (err) {
    // the client did not acknowledge the event in the given delay
    }
    });
    }
    }

    Related: #4595

  • 4.5.4 - 2022-11-22

    This release contains a bump of:

    Links:

  • 4.5.3 - 2022-10-15
  • 4.5.2 - 2022-09-02
  • 4.5.1 - 2022-05-17
  • 4.5.0 - 2022-04-23
  • 4.4.1 - 2022-01-06
  • 4.4.0 - 2021-11-18
from socket.io GitHub release notes
Commit messages
Package name: socket.io
  • 6ab2509 chore(release): 4.7.4
  • d9fb2f6 chore(tests): add a test for noArgs in a namespace
  • 2c0a81c chore(tests): fix issues due to client#id type change
  • f8d2644 chore(tests): add type defs for expectjs and fix invalid expectations
  • 04640d6 chore(tests): indicate a future ts error with version
  • cb6d2e0 fix(typings): calling io.emit with no arguments incorrectly errored
  • 80b2c34 chore: bump socket.io-client version
  • 0d89319 chore(release): 4.7.3
  • df8e70f fix: return the first response when broadcasting to a single socket (#4878)
  • 8c9ebc3 fix(typings): allow to bind to a non-secure Http2Server (#4853)
  • efb5c21 docs(examples): add Vue client with CRUD example
  • 3848280 docs(examples): upgrade basic-crud-application to Angular v17
  • 9a2a83f refactor: cleanup after merge
  • f6ef267 refactor(typings): improve emit types (#4817)
  • 1cdf36b test: build examples in the CI (#3856)
  • bbf1fdc docs: add Elephant.IO as PHP client library (#4779)
  • b4dc83e docs(examples): add codesandbox configuration
  • ccbb4c0 docs: add example with connection state recovery
  • d744fda docs: improve example with express-session
  • 8259cda docs: use io.engine.use() with express-session
  • fd9dd74 docs: use "connection" instead of "connect"
  • c332643 chore(release): 4.7.2
  • 3468a19 fix(webtransport): properly handle WebTransport-only connections
  • 09d4549 chore: bump engine.io to version 6.5.2

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@NOUIY @snyk-bot