Readest is a modern, feature-rich ebook reader designed for seamless cross-platform access and an…

Why it is Yellow

• CVSS 8.6 high

References

• https://github.com/readest/readest/commit/4025c4d7b52c8c174ec1d4c02c2a864cce249604
• https://github.com/readest/readest/commit/446c2c72de198de2dfcd63589f549ca517961d15
• https://github.com/readest/readest/pull/4639
• https://github.com/readest/readest/pull/4651
• https://github.com/readest/readest/releases/tag/v0.11.10
• https://github.com/readest/readest/security/advisories/GHSA-55vr-pvq5-6fmg

Original description

Readest is a modern, feature-rich ebook reader designed for seamless cross-platform access and an intuitive reading experience. In affected desktop Tauri builds prior to 0.11.10, the apps/readest-app/src-tauri/src/transfer_file.rs commands download_file and upload_file accepted a webview-controlled file_path and passed it to File::create or File::open without checking the Tauri filesystem scope, rejecting absolute paths, or blocking parent-directory traversal. The commands were registered in the global invoke handler for the main, updater, and reader-* windows, so JavaScript executing in the privileged application origin could write attacker-controlled content to any path writable by the process or read and send any path readable by the process. Exploitation requires JavaScript execution in that privileged origin, such as through an application XSS or compromised renderer; whether book-embedded JavaScript can reach the parent origin was not established. The write primitive can overwrite trusted or startup files, while the read primitive can expose keys, tokens, and application secrets. This issue is fixed in version 0.11.10.