### ImpactPion Interceptor versions v0.1.36 through v0.1.38 contain a bug in a RTP packet factory that can be exploited to trigger a panic with Pion based SFU via crafted RTP packets, This only affect users that use pion/interceptor.### PatchesUpgrade to v0.1.39 or later, which includes PR [#338](https://github.com/pion/interceptor/pull/338) which validates that: `padLen > 0 && padLen <= payloadLength` and return error on overflow, avoiding panic.If upgrading is not possible, apply the patch from the pull request manually or drop packets whose P-bit is set but whose padLen is zero or larger than the remaining payload.### WorkaroundsAt the application layer, reject any RTP packet where:```hasPadding (P-bit field) == true && (padLen == 0 || padLen > packetLen – headerLen)```before passing it to Pion’s packet factories.### ReferencesCommit fixing the bug: https://github.com/pion/interceptor/commit/fa5b35ea867389cec33a9c82fffbd459ca8958e5Pull request: https://github.com/pion/interceptor/pull/338Issue: https://github.com/pion/webrtc/issues/3148
Fix available through Seal Security. No upgrade required, protect your application instantly.
Fix without upgrading