The vulnerability allows an unauthenticated attacker to cause a denial of service by sending a specially crafted binary WebSocket message. The analysis of the provided patch commit 17939826efa20a97f087b3d390ec5136df350bae reveals that the fix is located in the server/channels/app/platform/web_conn.go file, within the WebConn.readPump function. This function is the primary loop for reading data from the WebSocket. The patch introduces a new check that explicitly rejects binary messages (msgType != websocket.TextMessage) if the connection is not authenticated (!wc.IsAuthenticated()). This indicates that the WebConn.readPump function was the entry point for the malicious payload. While the root cause is likely within the msgpack decoding library (as suggested by the go.mod and go.sum changes which update a forked msgpack library), the WebConn.readPump function is the function that would appear in a runtime profile as it's responsible for receiving and dispatching the incoming WebSocket frames. An exploit would trigger this function, which, prior to the patch, would then call the vulnerable decoding logic.