Destroying OAuth Applications doesn't notify Streaming of Access Tokens being destroyed in mastodon
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-613.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| mastodon | mastodon | 4.2.6 to before 4.2.6; 4.1.0 to before 4.1.14; 4.0.0 to before 4.0.14; before 3.5.18 | 4.2.6, 4.1.14, 4.0.14, 3.5.18 | Patch available | CNA |
- mastodon Vendormastodon Affected 4.2.6 to before 4.2.6; 4.1.0 to before 4.1.14; 4.0.0 to before 4.0.14; before 3.5.18 Fixed in 4.2.6, 4.1.14, 4.0.14, 3.5.18 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:joinmastodon:mastodon:*:*:*:*:*:*:*:* | before 3.5.18; 4.0.0 to before 4.0.14; 4.1.0 to before 4.1.14; 4.2.0 to before 4.2.6 | Vulnerable | mastodon |
- cpe:2.3:a:joinmastodon:mastodon:*:*:*:*:*:*:*:* Versions before 3.5.18; 4.0.0 to before 4.0.14; 4.1.0 to before 4.1.14; 4.2.0 to before 4.2.6 Vulnerable ·mastodon
Remediation
- Fix · CNA mastodon (mastodon) Fixed in 4.2.6, 4.1.14, 4.0.14, 3.5.18
Timeline
- 2026-10-02 Threatist record created from CVE-2024-25619
References
More Mastodon vulnerabilities
- TI-2022-02004 Improper Restriction of Excessive Authentication Attempts in mastodon/mastodon CVSS 3.1CRITICAL 9.8
- TI-2025-34613 Mastodon e‑mail throttle misconfiguration allows unlimited email confirmations against unconfirmed emails CVSS 3.1HIGH 7.5
- TI-2022-22936 Mastodon through 4.0.2 allows attackers to cause a denial of service (large Sidekiq pull… CVSS 3.1HIGH 7.5
- TI-2023-18301 Mastodon vulnerable to arbitrary file creation through media attachments CVSS 3.1CRITICAL 10.0
- TI-2023-13359 Mastodon's blind LDAP injection in login allows the attacker to leak arbitrary attributes from LDAP database CVSS 3.1HIGH 7.7
- TI-2024-16846 External OpenID Connect Account Takeover by E-Mail Change in mastodon CVSS 3.1HIGH 7.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences