Read the docs

Password verification bypass when logging into inactive accounts

Priority LOW 38CWE-287Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Security bypass
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-287.

Summary

### Summary A flaw in the log-in logic allowed a local user to switch to a different inactive local user mid-login, generating a sign-in token email for them without their password. They could then complete log-in as that different user, provided they manage to guess the sign-in token. ### Impact While this allows an attacker to bypass password authentication, the impact is limited by the fact that: - only accounts without a second-factor authentication could be targeted - only accounts with no activity within the past 3 months could be targeted - the attacker needs a valid local user - the attacker needs to brute-force the sign-in token, which essentially is a 6-characters base64 string

Why it matters now

Fix Fixed Mastodon: 5.0.0-alpha.4, 4.7.5

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Mastodon>= 4.8.0-alpha.3, < 5.0.0-alpha.35.0.0-alpha.4Patch availableGHSA-3xjw-gv43-3w62
—Mastodon4.7.44.7.5Patch availableGHSA-3xjw-gv43-3w62
  • Mastodon Vendor— Affected >= 4.8.0-alpha.3, < 5.0.0-alpha.3 Fixed in 5.0.0-alpha.4 Patch available GHSA-3xjw-gv43-3w62
  • Mastodon Vendor— Affected 4.7.4 Fixed in 4.7.5 Patch available GHSA-3xjw-gv43-3w62

Remediation

  • Fix · GHSA-3xjw-gv43-3w62 Mastodon Fixed in 5.0.0-alpha.4 Advisory →
  • Fix · GHSA-3xjw-gv43-3w62 Mastodon Fixed in 4.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-3xjw-gv43-3w62

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences