# CVE-2024-25619: Destroying OAuth Applications doesn't notify Streaming of Access Tokens being destroyed in mastodon

> Destroyed OAuth applications could continue streaming user data because the streaming server was not notified of token revocation.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** BIT-mastodon-2024-25619, GHSA-7w3c-p9j8-mq3x

## What is CVE-2024-25619?

CVE-2024-25619 is a low-severity missing authorization vulnerability in mastodon, published on 14 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release), CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2024-25619?

1 open source package ship an affected version, including mastodon. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mastodon` | Bitnami | All versions | 4.2.6 |

Products: Joinmastodon Mastodon.

## How do I fix CVE-2024-25619?

Upgrade mastodon to 4.2.6 or later.

## Is CVE-2024-25619 being exploited?

There is no known exploitation of CVE-2024-25619 in the wild and no public exploit code.

## Other vulnerabilities in mastodon

- [CVE-2023-36460](https://insights.sbomify.com/CVE-2023-36460/): Mastodon vulnerable to arbitrary file creation through media attachments (critical 10.0)
- [CVE-2022-2166](https://insights.sbomify.com/CVE-2022-2166/): Improper Restriction of Excessive Authentication Attempts in mastodon/mastodon (critical 9.8)
- [CVE-2022-24307](https://insights.sbomify.com/CVE-2022-24307/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-21018](https://insights.sbomify.com/CVE-2018-21018/): Auth bypass in n/a (critical 9.8)
- [CVE-2024-23832](https://insights.sbomify.com/CVE-2024-23832/): Mastodon Remote user impersonation and takeover (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25619 and fix it if it is affected.

What it is: CVE-2024-25619 is a low-severity missing authorization vulnerability in mastodon, published on 14 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25619 in the wild and no public exploit code.

Affected packages and fixed versions:
- mastodon (Bitnami): affected all versions; fixed in 4.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-25619/ (Markdown: https://insights.sbomify.com/CVE-2024-25619/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-25619
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-25619
- OSV: https://osv.dev/vulnerability/CVE-2024-25619

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-25619/
Summaries are generated and may contain mistakes; the official description above is the record.