chore(deps): update socket.io/client to get downstream security patches #628
+227
−113
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.
Why
[email protected]
(link) introduced an updated version ofengine.io-client
(link) that includes the updatedws
version that fixes this vulnerability CVE-2024-37890I haven't looked into whether the vulnerability affects this package, but because of the semver used in the
socket.io
packages, and in these packages, the vulnerable package wasn't able to be updated in our repo that usessnack-sdk
.How
I updated to the latest patch version of
socket.io-client
that included thews
fix. I had to make two minor TypeScript type changes but otherwise the changes insocket.io-client
seemed non-breaking (api additions and bug fixes).Test Plan
I see that the socket transport is mocked in the jest tests. Is there another way an update like this should be tested?