java-topology/defects/phoenix/patch/phoenix-0001-channel-dispatch-event-intercepts-mapset.patch

29 lines
1.4 KiB
Diff

From 2db25de Phoenix HEAD (2026-03-27)
Subject: [PATCH phoenix-0001] Fix CWE-407: store event_intercepts as MapSet for O(1) dispatch lookup
The fastlane tuple stores event_intercepts as a plain list (the result of
channel.__intercepts__(), which returns @phoenix_intercepts — a list).
In dispatch/3, `event in event_intercepts` is called once per subscriber per
broadcast. With N subscribers and K intercepted events this is O(N*K) list
scans. Storing as MapSet at subscribe time makes the per-dispatch check O(1).
No change to the `event in event_intercepts` expression is needed — Elixir's
`in` operator dispatches to Enumerable.member?/2, which for MapSet is O(1).
CWE-407: Algorithmic Complexity (Inefficient Algorithmic Complexity)
---
lib/phoenix/channel/server.ex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/phoenix/channel/server.ex b/lib/phoenix/channel/server.ex
index xxxxxxx..yyyyyyy 100644
--- a/lib/phoenix/channel/server.ex
+++ b/lib/phoenix/channel/server.ex
@@ -440,7 +440,7 @@ defmodule Phoenix.Channel.Server do
Process.monitor(transport_pid)
- fastlane = {:fastlane, transport_pid, serializer, channel.__intercepts__()}
+ fastlane = {:fastlane, transport_pid, serializer, MapSet.new(channel.__intercepts__())}
PubSub.subscribe(pubsub_server, topic, metadata: fastlane)
{:noreply, %{socket | joined: true}}