CVE-2024-25619
Description
Mastodon is a free, open-source social network server based on ActivityPub. When an OAuth Application is destroyed, the streaming server wasn't being informed that the Access Tokens had also been destroyed, this could have posed security risks to users by allowing an application to continue listening to streaming after the application had been destroyed. Essentially this comes down to the fact that when Doorkeeper sets up the relationship between Applications and Access Tokens, it uses a `dependent: delete_all` configuration, which means the `after_commit` callback setup on `AccessTokenExtension` didn't actually fire, since `delete_all` doesn't trigger ActiveRecord callbacks. To mitigate, we need to add a `before_destroy` callback to `ApplicationExtension` which announces to streaming that all the Application's Access Tokens are being "killed". Impact should be negligible given the affected application had to be owned by the user. None the less this issue has been addressed in versions 4.2.6, 4.1.14, 4.0.14, and 3.5.18. Users are advised to upgrade. There are no known workaround for this vulnerability.
How to fix
- joinmastodon mastodon3.5.18, 4.0.14, 4.1.14, 4.2.6 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| joinmastodon mastodon | v < 3.5.18, 4.0.0 ≤ v < 4.0.14, 4.1.0 ≤ v < 4.1.14, 4.2.0 ≤ v < 4.2.6 | 3.5.18, 4.0.14, 4.1.14, 4.2.6 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.