pion interceptor up to 0.1.38 RTP allocation of resources

Summaryinfo

A vulnerability was found in pion interceptor up to 0.1.38. It has been classified as problematic. This issue affects some unknown processing of the component RTP Handler. Performing a manipulation results in allocation of resources. This vulnerability is cataloged as CVE-2025-49140. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in pion interceptor up to 0.1.38. This affects an unknown code block of the component RTP Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:

Pion Interceptor is a framework for building RTP/RTCP communication software. 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. Users should upgrade to v0.1.39 or later, 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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-49140 since 06/02/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 0.1.39 eliminates this vulnerability. Applying the patch fa5b35ea867389cec33a9c82fffbd459ca8958e5 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-17569). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• pion

Name

• interceptor

Version

• 0.1.0
• 0.1.1
• 0.1.2
• 0.1.3
• 0.1.4
• 0.1.5
• 0.1.6
• 0.1.7
• 0.1.8
• 0.1.9
• 0.1.10
• 0.1.11
• 0.1.12
• 0.1.13
• 0.1.14
• 0.1.15
• 0.1.16
• 0.1.17
• 0.1.18
• 0.1.19
• 0.1.20
• 0.1.21
• 0.1.22
• 0.1.23
• 0.1.24
• 0.1.25
• 0.1.26
• 0.1.27
• 0.1.28
• 0.1.29
• 0.1.30
• 0.1.31
• 0.1.32
• 0.1.33
• 0.1.34
• 0.1.35
• 0.1.36
• 0.1.37
• 0.1.38

License

• open-source

Website

• Product: https://github.com/pion/interceptor/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion