[Snyk] Upgrade socket.io from 1.7.4 to 4.5.2 #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade socket.io from 1.7.4 to 4.5.2.
ℹ️ 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.
Warning: This is a major version upgrade, and may be a breaking change.
The recommended version fixes:
npm:parsejson:20170908
Why? CVSS 7.5
SNYK-JS-SOCKETIOPARSER-1056752
Why? CVSS 7.5
SNYK-JS-ENGINEIO-1056749
Why? CVSS 7.5
SNYK-JS-WS-1296835
Why? CVSS 7.5
SNYK-JS-SOCKETIO-1024859
Why? CVSS 7.5
npm:ms:20170412
Why? CVSS 7.5
npm:ms:20170412
Why? CVSS 7.5
npm:debug:20170905
Why? CVSS 7.5
npm:debug:20170905
Why? CVSS 7.5
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: socket.io
Bug Fixes
Links:
~6.2.0
~8.2.3
Bug Fixes
Links:
~6.2.0
~8.2.3
Bug Fixes
Features
This is similar to
onAny()
, but for outgoing packets.Syntax:
Syntax:
So that clients in HTTP long-polling can decide how many packets they have to send to stay under the maxHttpBufferSize
value.
This is a backward compatible change which should not mandate a new major revision of the protocol (we stay in v4), as
we only add a field in the JSON-encoded handshake data:
Links:
~6.2.0
(diff)~8.2.3
Bug Fixes
RemoteSocket.data
type safe (#4234) (770ee59)SocketData
type to custom namespaces (#4233) (f2b8de7)Links:
~6.1.0
(diff)~8.2.3
Bug Fixes
Features
const { Server } = require("socket.io");
const app = new App();
const io = new Server();
io.attachApp(app);
io.on("connection", (socket) => {
// ...
});
app.listen(3000, (token) => {
if (!token) {
console.warn("port already in use");
}
});
socket.data
(#4159) (fe8730c)name: string;
age: number;
}
const io = new Server<ClientToServerEvents, ServerToClientEvents, InterServerEvents, SocketData>();
io.on("connection", (socket) => {
socket.data.name = "john";
socket.data.age = 42;
});
Links:
~6.1.0
(diff)~8.2.3
Bug Fixes
Links:
~6.0.0
~8.2.3
Bug Fixes
Links:
~6.0.0
~8.2.3
For this release, most of the work was done on the client side, see here.
Bug Fixes
Features
Links:
~6.0.0
(diff)~8.2.3
(diff)The default value of the
maxHttpBufferSize
option has been decreased from 100 MB to 1 MB, in order to prevent attacks by denial of service.Security advisory: GHSA-j4f2-536g-r55m
Bug Fixes
Links:
~3.6.0
(diff)~7.4.2
Commit messages
Package name: socket.io
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