Streambert vulnerabilities

Streambert before 2.5.0 improperly validates executable paths supplied to the run-download IPC handler, allowing a compromised renderer to execute arbitrary local binaries with the app's privileges.

Streambert before 2.5.0 has an unvalidated auto-updater URL vulnerability that allows a compromised renderer to make the main process download and execute an arbitrary binary, resulting in remote code execution.

In Streambert versions 2.4.0 and prior, a Zip Slip vulnerability was identified in the subtitle extraction logic. The application does not sanitize archive entry filenames during extraction, allowing for path traversal attacks and writing arbitrary files to the host filesystem.

Vulnerability in Streambert (before 2.6.0) in the open-external IPC handler, which passes a renderer-supplied URL to shell.openExternal without protocol validation. A compromised renderer can open local files or launch applications.

Vulnerability in Streambert (before 2.6.0) in the open-path-at-time IPC handler, which passes a renderer-controlled file path to shell.openPath without validation. A compromised renderer can launch a local executable or script.

Vulnerability in Streambert (before 2.6.0) in the perform-scheduled-backup IPC handler, which uses a renderer-supplied path for file operations without checking if it is in an authorized location. A compromised renderer can create directories, write files, and delete files anywhere.

Vulnerability in Streambert (from 2.5.0 to 2.6.0) allows script injection in the Wyzie key redemption window, which removes the CSP header and lacks window open restrictions, enabling malicious script execution in the application context.

Vulnerability in Streambert (before 2.5.0) in the downloadSubtitleFile function, which accepts a renderer-supplied URL with file: scheme and copies the file to a chosen location. A compromised renderer can copy any file readable by the StreamBERT process.