Finding Name | Summary | Recommendation |
---|---|---|
Due to usage of |
This issue can be fixed in multiple ways, depending on the importance of HTML content being rendered.
OR
We recommend to disable the HTML input, as the sanitization process is only meant to reduce but not to erase the risk of unwanted HTML to be processed and rendered. |
|
The custom implemented Tauri command |
2
API Reference, requires a custom regex to allow only file paths |
|
The |
Refactor the workflow to facilitate proper github authorisation mechanisms. |
|
The application facilitates a permissive allow list configuration, which imports and enables unused Tauri API endpoints. |
we recommend to use the following allow list:
In general we recommend to only enable the specific features, which are used and imported in the frontend code. |
|
Application dependencies have their own telemetry system, which is not documented, disabled or controlled by the bloop application. |
|
|
The application is missing a Content Security policy to add a defense-in-depth layer against adversaries. |
|
|
Due to outdated packages in the frontend, the application is at risk of vulnerabilities in these dependencies. |
|
|
Some of the Rust crates possess vulnerabilies or are unmaintained. The application is at risk through these dependencies. |
|