Bazarr's UI login and API key guard separate automation paths
Bazarr, a tool that manages subtitle search and sync for media libraries, exposes a web UI and a REST API that serve different clients, so security reviews should evaluate them separately. A correctly configured login page does not protect an API key that a script or integration still holds. Bazarr also uses separate API keys to connect to Sonarr and Radarr, and those keys should not be treated as interchangeable. The article advises mapping every connection as a trust edge, scoping keys to the smallest integration, and testing unauthenticated, keyless, valid-key and revoked-key requests. It further notes that Bazarr webhooks authenticate with the API key rather than signed requests, so receivers need network boundaries or extra verification.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in