Server-side request forgery in iSponsorBlockTV device discovery
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
iSponsorBlockTV before 2.11.0 trusts the SSDP LOCATION URL from a local network responder without checking its destination (CWE-918). An attacker on the local network can spoof an SSDP response during automatic discovery and make the client send requests to internal services. The attacker does not see responses or errors, so the impact is blind server-side request forgery with limited integrity impact.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
iSponsorBlockTV is a SponsorBlock client for YouTube TV clients. Prior to 2.11.0, src/iSponsorBlockTV/dial_client.py trusts the SSDP LOCATION URL supplied by a local-network responder without validating its destination. During automatic discovery, this can cause an attacker-directed GET request and a constrained POST request to a path ending in /YouTube; the POST uses application-defined headers and an application-defined payload rather than attacker-selected request contents. The requests can reach internal services, but the detailed request behavior states that response data and errors are not returned to the attacker, making the demonstrated behavior blind SSRF with bounded integrity impact. This issue is fixed in version 2.11.0.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade iSponsorBlockTV to version 2.11.0, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA iSponsorBlockTV (dmunozv04) Fixed in 2.11.0
Timeline
- 2026-11-16 Threatist record created from CVE-2026-77597
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences