Skip to content

Commit

Permalink
blog: CVE-2024-4576 Blog Post (#2060)
Browse files Browse the repository at this point in the history
* added new security blog post

* fix metadata

* ❤️
  • Loading branch information
tillmann-crabnebula authored Apr 10, 2024
1 parent ef0ead2 commit 3730f3e
Show file tree
Hide file tree
Showing 3 changed files with 53 additions and 0 deletions.
5 changes: 5 additions & 0 deletions astro.config.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,11 @@ const authors = {
title: 'Tauri Development Lead',
picture: '/authors/wusyong.png',
},
chip: {
name: 'Chip Reed',
title: 'Tauri Security',
picture: '/authors/chip.png',
},
};

const site = 'https://beta.tauri.app';
Expand Down
Binary file added public/authors/chip.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
48 changes: 48 additions & 0 deletions src/content/docs/blog/cve-2024-24576.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
---
title: Rust Security Advisory CVE-2024-24576
date: 2024-04-10
authors: [tweidinger, chip]
excerpt: Recent Rust Security Advisory CVE-2024-24576.
banner:
content: |
You're reading the blog on the prerelease site for Tauri 2.0 -
<a href="https://tauri.app">Go to the Tauri 1.0 site</a>
---

The Rust Security Response WG announced [`CVE-2024-24576`](https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html), which affects the Rust Standard Library on Windows.

> TL;DR: Upgrade your Rust version to `1.77.2`.
## How Does it Affect Tauri as a Library?

Some Tauri organization repositories use batch files (`cmd.exe` under the hood) for developer environment tooling such as build scripts.
No reviewed repositories use batch files for runtime code.

We don't see additional risks for the Tauri project based on this CVE.

Nevertheless, we will update our CI systems to use the latest Rust version.

## Is My Tauri App Affected?

In general you are possibly affected if you fulfil **all** of the below criteria:

- You ship your app on **Windows**
- Your project enables the Tauri v1 [`shell`](https://tauri.app/v1/api/js/shell/) feature with `"execute": true` or the v2 [`shell-plugin`](https://github.com/tauri-apps/plugins-workspace/tree/v2/plugins/shell) with `allow-execute` permission
- You allow arguments in the `scope` element of the `shell` feature
- **You pass untrusted input to `cmd.exe` or `.bat`/`.cmd` files and improperly validate the scope** (🚩)

If any of these criteria are not fulfilled in your application you are likely **NOT** affected.

If you implement custom commands or logic written in your application that directly exposes the Rust `Command` with arguments provided at runtime, you may be affected.
While not Tauri specific, this pattern could affect any Rust project.

## Conclusion

Please upgrade your Rust version to `1.77.2`
as soon as possible and distribute updates to your users.

This investigation and writeup was performed in coorporation with our partner [CrabNebula](https://crabnebula.dev/blog/cve-2024-24576/) ❤️.

---
[Read more about this security advisory here](https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/).
This affects many programming languages, this specific CVE is just the one filed for Rust.

0 comments on commit 3730f3e

Please sign in to comment.