Nixpkgs Security Tracker

Login with GitHub

Suggestions search

With package: mastodon

Found 3 matching suggestions

View:
Compact
Detailed
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    11 packages
    • mastodon-bot
    • bitlbee-mastodon
    • mastodon-archive
    • nodePackages.mastodon-bot
    • python312Packages.mastodon-py
    • python313Packages.mastodon-py
    • python314Packages.mastodon-py
    • nodePackages_latest.mastodon-bot
    • home-assistant-component-tests.mastodon
    • tests.home-assistant-component-tests.mastodon
    • wordpressPackages.plugins.simple-mastodon-verification
  • @LeSuisse removed
    4 maintainers
    • @Izorkin
    • @ghuntley
    • @happy-river
    • @erictapen
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Mastodon has SSRF via unvalidated FASP Provider base_url

Mastodon is a free, open-source social network server based on ActivityPub. FASP registration requires manual approval by an administrator. In versions 4.4.0 through 4.4.13 and 4.5.0 through 4.5.6, an unauthenticated attacker can register a FASP with an attacker-chosen `base_url` that includes or resolves to a local / internal address, leading to the Mastodon server making requests to that address. This only affects Mastodon servers that have opted in to testing the experimental FASP feature by setting the environment variable `EXPERIMENTAL_FEATURES` to a value including `fasp`. An attacker can force the Mastodon server to make http(s) requests to internal systems. While they cannot control the full URL that is being requested (only the prefix) and cannot see the result of those requests, vulnerabilities or other undesired behavior could be triggered in those systems. The fix is included in the 4.4.14 and 4.5.7 releases. Admins that are actively testing the experimental "fasp" feature should update their systems. Servers not using the experimental feature flag `fasp` are not affected.

Affected products

mastodon
  • ==>= 4.5.0, < 4.5.7
  • ==>= 4.4.0, < 4.4.14

Matching in nixpkgs

Ignored packages (11)

pkgs.mastodon-bot

Bot to publish twitter, tumblr or rss posts to an mastodon account.

Package maintainers

Ignored maintainers (4)
Upstream advisory: https://github.com/mastodon/mastodon/security/advisories/GHSA-46w6-g98f-wxqm
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    11 packages
    • mastodon-bot
    • bitlbee-mastodon
    • mastodon-archive
    • nodePackages.mastodon-bot
    • python312Packages.mastodon-py
    • python313Packages.mastodon-py
    • python314Packages.mastodon-py
    • nodePackages_latest.mastodon-bot
    • home-assistant-component-tests.mastodon
    • tests.home-assistant-component-tests.mastodon
    • wordpressPackages.plugins.simple-mastodon-verification
  • @LeSuisse removed
    4 maintainers
    • @Izorkin
    • @ghuntley
    • @happy-river
    • @erictapen
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Mastodon may allow unconfirmed FASP to make subscriptions

Mastodon is a free, open-source social network server based on ActivityPub. FASP registration requires manual approval by an administrator. In versions 4.4.0 through 4.4.13 and 4.5.0 through 4.5.6, actions performed by a FASP to subscribe to account/content lifecycle events or to backfill content did not check properly whether the FASP was actually approved. This only affects Mastodon servers that have opted in to testing the experimental FASP feature by setting the environment variable `EXPERIMENTAL_FEATURES` to a value including `fasp`. An attacker can make subscriptions and request content backfill without approval by an administrator. Done once, this leads to minor information leak of URIs that are publicly available anyway. But done several times this is a serious vector for DOS, putting pressure on the sidekiq worker responsible for the `fasp` queue. The fix is included in the 4.4.14 and 4.5.7 releases. Admins that are actively testing the experimental "fasp" feature should update their systems. Servers not using the experimental feature flag `fasp` are not affected.

Affected products

mastodon
  • ==>= 4.5.0, < 4.5.7
  • ==>= 4.4.0, < 4.4.14

Matching in nixpkgs

Ignored packages (11)

pkgs.mastodon-bot

Bot to publish twitter, tumblr or rss posts to an mastodon account.

Package maintainers

Ignored maintainers (4)
Upstream advisory: https://github.com/mastodon/mastodon/security/advisories/GHSA-qgmm-vr4c-ggjg
Permalink CVE-2026-25540
6.5 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): LOW
  • Integrity impact (I): NONE
  • Availability impact (A): LOW
updated 1 month, 3 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    11 packages
    • mastodon-bot
    • bitlbee-mastodon
    • mastodon-archive
    • nodePackages.mastodon-bot
    • python312Packages.mastodon-py
    • python313Packages.mastodon-py
    • python314Packages.mastodon-py
    • nodePackages_latest.mastodon-bot
    • home-assistant-component-tests.mastodon
    • tests.home-assistant-component-tests.mastodon
    • wordpressPackages.plugins.simple-mastodon-verification
  • @LeSuisse removed
    9 maintainers
    • @ju1m
    • @erictapen
    • @ghuntley
    • @dotlambda
    • @fabaff
    • @jpotier
    • @mweinelt
    • @Izorkin
    • @happy-river
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Mastodon's signature-dependent ActivityPub collection responses cached under signature-independent keys (Web Cache Poisoning via `Rails.cache`)

Mastodon is a free, open-source social network server based on ActivityPub. Prior to versions 4.3.19, 4.4.13, 4.5.6, Mastodon is vulnerable to web cache poisoning via `Rails.cache. When AUTHORIZED_FETCH is enabled, the ActivityPub endpoints for pinned posts and featured hashtags have contents that depend on the account that signed the HTTP request. However, these contents are stored in an internal cache and reused with no regards to the signing actor. As a result, an empty response generated for a blocked user account may be served to requests from legitimate non-blocked actors, or conversely, content intended for non-blocked actors may be returned to blocked actors. This issue has been patched in versions 4.3.19, 4.4.13, 4.5.6.

Affected products

mastodon
  • ==< 4.3.19
  • ==< 4.4.13
  • ==< 4.5.6

Matching in nixpkgs

Package maintainers

Ignored maintainers (4)
Fixed in https://github.com/NixOS/nixpkgs/pull/486583 (unstable) and https://github.com/NixOS/nixpkgs/pull/486671 (25.11)