mirror of
https://akkoma.dev/AkkomaGang/akkoma.git
synced 2024-11-09 09:52:13 +00:00
0c2b33458d
In Mastodon media can only be used by owners and only be associated with
a single post. We currently allow media to be associated with several
posts and until now did not limit their usage in posts to media owners.
However, media update and GET lookup was already limited to owners.
(In accordance with allowing media reuse, we also still allow GET
lookups of media already used in a post unlike Mastodon)
Allowing reuse isn’t problematic per se, but allowing use by non-owners
can be problematic if media ids of private-scoped posts can be guessed
since creating a new post with this media id will reveal the uploaded
file content and alt text.
Given media ids are currently just part of a sequentieal series shared
with some other objects, guessing media ids is with some persistence
indeed feasible.
E.g. sampline some public media ids from a real-world
instance with 112 total and 61 monthly-active users:
17.465.096 at t0
17.472.673 at t1 = t0 + 4h
17.473.248 at t2 = t1 + 20min
This gives about 30 new ids per minute of which most won't be
local media but remote and local posts, poll answers etc.
Assuming the default ratelimit of 15 post actions per 10s, scraping all
media for the 4h interval takes about 84 minutes and scraping the 20min
range mere 6.3 minutes. (Until the preceding commit, post updates were
not rate limited at all, allowing even faster scraping.)
If an attacker can infer (e.g. via reply to a follower-only post not
accessbile to the attacker) some sensitive information was uploaded
during a specific time interval and has some pointers regarding the
nature of the information, identifying the specific upload out of all
scraped media for this timerange is not impossible.
Thus restrict media usage to owners.
Checking ownership just in ActivitDraft would already be sufficient,
since when a scheduled status actually gets posted it goes through
ActivityDraft again, but would erroneously return a success status
when scheduling an illegal post.
Independently discovered and fixed by mint in Pleroma
|
||
|---|---|---|
| .. | ||
| activity | ||
| akkoma | ||
| collections | ||
| config | ||
| conversation | ||
| docs | ||
| ecto_type/activity_pub/object_validators | ||
| emails | ||
| emoji | ||
| http | ||
| instances | ||
| integration | ||
| mfa | ||
| migration_helper | ||
| object | ||
| password | ||
| repo/migrations | ||
| search | ||
| translators | ||
| upload | ||
| uploaders | ||
| user | ||
| web | ||
| workers | ||
| activity_test.exs | ||
| announcement_read_relationship_test.exs | ||
| announcement_test.exs | ||
| application_requirements_test.exs | ||
| bookmark_test.exs | ||
| captcha_test.exs | ||
| config_db_test.exs | ||
| config_test.exs | ||
| conversation_test.exs | ||
| emoji_test.exs | ||
| filter_test.exs | ||
| following_relationship_test.exs | ||
| formatter_test.exs | ||
| frontend_test.exs | ||
| hashtag_test.exs | ||
| healthcheck_test.exs | ||
| html_test.exs | ||
| http_test.exs | ||
| instances_test.exs | ||
| iso639_test.exs | ||
| job_queue_monitor_test.exs | ||
| keys_test.exs | ||
| list_test.exs | ||
| marker_test.exs | ||
| mfa_test.exs | ||
| moderation_log_test.exs | ||
| notification_test.exs | ||
| object_test.exs | ||
| otp_version_test.exs | ||
| pagination_test.exs | ||
| password_test.exs | ||
| registration_test.exs | ||
| repo_test.exs | ||
| report_note_test.exs | ||
| reverse_proxy_test.exs | ||
| runtime_test.exs | ||
| safe_jsonb_set_test.exs | ||
| scheduled_activity_test.exs | ||
| signature_test.exs | ||
| stats_test.exs | ||
| upload_test.exs | ||
| user_invite_token_test.exs | ||
| user_note_test.exs | ||
| user_relationship_test.exs | ||
| user_search_test.exs | ||
| user_test.exs | ||
| utils_test.exs | ||
| xml_builder_test.exs | ||