Categories
CVE-2026-45327 high CVSS 8.2

Vulnerability in github.com/DatanoiseTV/tinyice (CVE-2026-45327)

Summary

Vulnerability in github.com/DatanoiseTV/tinyice (CVE-2026-45327). Data can be tampered with by attackers. Exploitable via POST /webrtc/source-offer. Mitigation: upgrade to 2.5.0 or later.

Original description

The description as published by the source.

TinyIce is a streaming server for audio and video. In versions 0.8.95 through 2.4.1, missing authentication on WebRTC ingest endpoint allows unauthenticated stream injection. Version 2.5.0 fixes the issue by requiring either HTTP Basic auth or a ?password= query parameter, comparing the supplied password against the per-mount source password (or the default_source_password fallback) using bcrypt, hooking into the existing brute-force IP rate-limiter (5 failed attempts per IP within 15 minutes triggers a lockout), and rejecting requests for mounts in disabled_mounts. The same release also tightens an adjacent endpoint, POST /admin/golive/chunk, which previously required session authentication but did not verify the session user's per-mount access nor check the CSRF token.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45327 has been found in github.com/DatanoiseTV/tinyice.
Attackers can target a specific entry point like POST /webrtc/source-offer over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade github.com/DatanoiseTV/tinyice to 2.5.0 or later.
If unsure, ask your IT team or search "github.com/DatanoiseTV/tinyice CVE-2026-45327" on the vendor's site.

CVE-2026-45327 (github.com/DatanoiseTV/tinyice) — CWE-306 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /webrtc/source-offer / POST /admin/golive/chunk / e2b60d6 / handleWebRTCSourceOffer
Patched: 2.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-306) exists in github.com/DatanoiseTV/tinyice. Attackers reach the vulnerable code path via POST /webrtc/source-offer without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/DatanoiseTV/tinyice. Attack surface: POST /webrtc/source-offer / POST /admin/golive/chunk / e2b60d6 / handleWebRTCSourceOffer.

🔥 Severity

Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.5.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /webrtc/source-offer requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/DatanoiseTV/tinyice' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/DatanoiseTV/tinyice' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/DatanoiseTV/tinyice を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /webrtc/source-offer' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /webrtc/source-offer への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade github.com/DatanoiseTV/tinyice to 2.5.0

    ステージング環境で 2.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /webrtc/source-offer on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/DatanoiseTV/tinyice
[{"type":"SEMVER","events":[{"introduced":"0.8.95"},{"fixed":"2.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details