Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| phoenixframework | phoenix | unaffected |
|
|||||||||||||||
| phoenixframework | phoenix | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Phoenixframework | Phoenix |
|
||||||||||||||||||||||||||||
| Phoenixframework | Phoenix |
|
Vendor Workaround
Reject the V1 serializer by listing only the V2 serializer on each socket: socket "/socket", MyAppWeb.UserSocket, websocket: [serializer: [{Phoenix.Socket.V2.JSONSerializer, "~> 2.0.0"}]], longpoll: [serializer: [{Phoenix.Socket.V2.JSONSerializer, "~> 2.0.0"}]] Clients that connect without a vsn parameter or with vsn=1.0.0 are then refused.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Uncaught Exception vulnerability in phoenixframework phoenix allows an unauthenticated attacker to cause a denial of service via a client-selected legacy serializer on binary channel broadcasts. When an application broadcasts {:binary, data} payloads on a channel topic, any client that connects without a vsn parameter, or with vsn=1.0.0, and joins that topic makes those broadcasts fail. Phoenix.Channel.Server.send/4 encodes each broadcast with every subscriber's own serializer inside the PubSub dispatch loop, calling fastlane!/1 with no rescue, and the negotiated Phoenix.Socket.V1.JSONSerializer raises Protocol.UndefinedError on a binary payload. Every binary broadcast on the topic then crashes the broadcasting process and skips every subscriber dispatched after the attacker. For broadcasts arriving from other nodes the loop runs in the PubSub adapter worker, whose repeated crashes restart the PubSub supervisor and empty the node's subscription registry while sockets stay connected. This issue affects phoenix: from 1.5.7 before 1.5.16, from 1.6.0-rc.0 before 1.6.18, from 1.7.0-rc.0 before 1.7.25, and from 1.8.0-rc.0 before 1.8.17. | |
| Title | Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads | |
| First Time appeared |
Phoenixframework
Phoenixframework phoenix |
|
| Weaknesses | CWE-248 | |
| CPEs | cpe:2.3:a:phoenixframework:phoenix:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Phoenixframework
Phoenixframework phoenix |
|
| References |
|
|
| Metrics |
cvssV4_0
|
Uncaught Exception