Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact An attacker can cause the creation of unnecessary background threads in the python-engineio server by exploiting the heartbeat mechanism, which launches a thread when a new connection is received, and when the client sends a PONG packet. Note: this issue primarily affects synchronous servers. Asynchronous servers allocate background tasks instead of physical threads, which are lightweight and less likely to cause denial of service. However, the fix that was implemented was also applied to the asynchronous case. Patches Version 4.13.2 addresses this issue as follows: - The initial background thread (or async task( for heartbeat management is only launched if a client passes authentication in the connect handler. - The server now ensures that there is only one background heatbeat thread (or async task) per client at a given point in time. Out of sequence PONG packets are now discarded when an active heartbeat thread is already running.
Recommended action: Upgrade to 4.13.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact There are two specific configurations of the python-engineio server in which the size of incoming messages is not checked before the messages are loaded into memory. An attacker can take advantage of these to cause unnecessary memory allocations in the python-engineio server. The two cases are: - POST requests, when using ASGI with the long polling transport - WebSocket messages, when using Aiohttp with the WebSocket transport Patches Version 4.13.2 addresses this issue as follows: - ASGI severs now only load the body of incoming requests into memory after the client is confirmed to be known and authenticated, and the payload size is below the maximum allowed size. Requests that do not comply with these requirements are discarded. - Aiohttp servers configure the maximum payload size in the underlying WebSocket layer from Aiohttp, so that large messages are discarded by Aiohttp before they are delivered to python-engineio.
Recommended action: Upgrade to 4.13.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
WebSocket cross-origin vulnerability Impact This is a Cross-Site Request Forgery (CSRF) vulnerability. It affects Socket.IO and Engine.IO web servers that authenticate clients using cookies. Patches python-engineio version 3.9.0 patches this vulnerability by adding server-side Origin header checks. Workarounds Do not use cookies for client authentication, or else add a CSRF token to the connection URL. References https://www.owasp.org/index.php/Cross-SiteRequestForgery(CSRF) https://www.christian-schneider.net/CrossSiteWebSocketHijacking.html For more information If you have any questions or comments about this advisory: Open an issue in python-engineio
Recommended action: Upgrade to 3.9.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.