First published: Wed Feb 14 2024(Updated: )
Mastodon is a free, open-source social network server based on ActivityPub. Mastodon allows new identities from configured authentication providers (CAS, SAML, OIDC) to attach to existing local users with the same e-mail address. This results in a possible account takeover if the authentication provider allows changing the e-mail address or multiple authentication providers are configured. When a user logs in through an external authentication provider for the first time, Mastodon checks the e-mail address passed by the provider to find an existing account. However, using the e-mail address alone means that if the authentication provider allows changing the e-mail address of an account, the Mastodon account can immediately be hijacked. All users logging in through external authentication providers are affected. The severity is medium, as it also requires the external authentication provider to misbehave. However, some well-known OIDC providers (like Microsoft Azure) make it very easy to accidentally allow unverified e-mail changes. Moreover, OpenID Connect also allows dynamic client registration. 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 workarounds for this vulnerability.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Mastodon | <3.5.18 | |
Mastodon | >=4.0.0<4.0.14 | |
Mastodon | >=4.1.0<4.1.14 | |
Mastodon | >=4.2.0<4.2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-25618 is considered a high severity vulnerability due to the potential for account takeover.
To fix CVE-2024-25618, upgrade to Mastodon version 4.0.14 or later.
CVE-2024-25618 affects Mastodon versions prior to 4.0.14 and certain intermediate versions between 3.5.18 and 4.2.6.
CVE-2024-25618 is a vulnerability allowing for possible account takeover through user authentication misconfiguration.
It is not recommended to continue using your current version of Mastodon if it is affected by CVE-2024-25618 due to the security risks involved.