Attack Chain

1. The attacker identifies a target mount point on a TinyIce server. Mount names are often public, appearing in directory listings, player URLs, and YP listings.
2. The attacker crafts a malicious SDP (Session Description Protocol) offer for a WebRTC connection.
3. The attacker sends an HTTP POST request to the /webrtc/source-offer endpoint, including the target mount point as a query parameter (?mount=<mount>) and the malicious SDP offer in the request body.
4. The vulnerable TinyIce server, lacking authentication, processes the malicious SDP offer via WebRTCManager.HandleSourceOffer.
5. The server establishes a WebRTC peer connection with the attacker.
6. The attacker publishes arbitrary audio (Opus) and video (H.264) tracks via the established WebRTC connection.
7. The TinyIce server broadcasts the attacker’s injected audio/video content to all listeners subscribed to the target mount point.
8. Listeners receive the attacker’s injected stream instead of the legitimate source’s content, resulting in a broadcast hijack.

Impact

Successful exploitation allows an attacker to inject arbitrary audio and video content into live broadcasts, effectively hijacking the stream. This can be used to broadcast silence, disruptive noise, malicious content, or competitor branding. While the legitimate publisher can attempt to re-establish their session, the attacker can immediately reconnect, leading to a sustained broadcast hijack until manual intervention occurs. The CVSS 3.1 base score is 7.4 (High), emphasizing the potential for significant integrity impact.

Recommendation

• Upgrade TinyIce to version 2.5.0 or later to apply the patch that fixes CVE-2026-45327.
• Implement the workaround by blocking POST /webrtc/source-offer at the reverse proxy to prevent unauthorized access to the vulnerable endpoint.
• Deploy the Sigma rule “Detect TinyIce WebRTC Unauthenticated SDP Offer” to identify potential exploitation attempts in webserver logs.
• Deploy the Sigma rule “Detect TinyIce Authentication Failure for WebRTC Source” to monitor for failed authentication attempts after patching or applying workarounds.