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.

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

chore(deps): update dependency engine.io to 4.1.2 [security] #384

Merged
merged 1 commit into from
May 23, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change
engine.io 4.1.1 -> 4.1.2

GitHub Vulnerability Alerts

CVE-2022-21676

Impact

A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.

RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear
at Receiver.getInfo (/.../node_modules/ws/lib/receiver.js:176:14)
at Receiver.startLoop (/.../node_modules/ws/lib/receiver.js:136:22)
at Receiver._write (/.../node_modules/ws/lib/receiver.js:83:10)
at writeOrBuffer (internal/streams/writable.js:358:12)

This impacts all the users of the engine.io package starting from version 4.0.0, including those who uses depending packages like socket.io.

Patches

A fix has been released for each major branch:

Version range Fixed version
engine.io@4.x.x 4.1.2
engine.io@5.x.x 5.2.1
engine.io@6.x.x 6.1.1

Previous versions (< 4.0.0) are not impacted.

For socket.io users:

Version range engine.io version Needs minor update?
socket.io@4.4.x ~6.1.0 -
socket.io@4.3.x ~6.0.0 Please upgrade to socket.io@4.4.x
socket.io@4.2.x ~5.2.0 -
socket.io@4.1.x ~5.1.1 Please upgrade to socket.io@4.4.x
socket.io@4.0.x ~5.0.0 Please upgrade to socket.io@4.4.x
socket.io@3.1.x ~4.1.0 -
socket.io@3.0.x ~4.0.0 Please upgrade to socket.io@3.1.x or socket.io@4.4.x (see here)

In most cases, running npm audit fix should be sufficient. You can also use npm update engine.io --depth=9999.

Workarounds

There is no known workaround except upgrading to a safe version.

For more information

If you have any questions or comments about this advisory:

Thanks to Marcus Wejderot from Mevisio for the responsible disclosure.


Configuration

📅 Schedule: "" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency engine.io to 4.1.2 [security] chore(deps): update dependency engine.io to 4.1.2 [security] - autoclosed May 16, 2022
@renovate renovate bot closed this May 16, 2022
@renovate renovate bot deleted the renovate/npm-engine.io-vulnerability branch May 16, 2022 18:28
@renovate renovate bot changed the title chore(deps): update dependency engine.io to 4.1.2 [security] - autoclosed chore(deps): update dependency engine.io to 4.1.2 [security] May 22, 2022
@renovate renovate bot reopened this May 22, 2022
@renovate renovate bot restored the renovate/npm-engine.io-vulnerability branch May 22, 2022 00:25
@jbolda
Copy link
Owner

jbolda commented May 23, 2022

bors merge

@bors bors bot merged commit 816c87b into main May 23, 2022
@bors
Copy link
Contributor

bors bot commented May 23, 2022

Build succeeded:

@bors bors bot deleted the renovate/npm-engine.io-vulnerability branch May 23, 2022 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants