Skip to content

Possibility of a fake account on a domain with arbitrary user content

Moderate
aumetra published GHSA-xmw2-875x-rq88 Oct 28, 2023

Package

No package listed

Affected versions

<=0.0.1-pre.4

Patched versions

>0.0.1-pre.5

Description

Summary

An attacker can make a Kitsune server recognize that they have an account with arbitrary content on a victim server's domain, if the victim server allows arbitrary users to upload documents.

Details

Kitsune's ActivityPub fetcher doesn't check the response's Content-Type, and accepts it even if the server doesn't mean that it's an Activity Streams document.

Affected code:

There are some possible solutions to this problem:

  • Check Content-Type of the response
  • Mandate WebFinger support on the federating servers (like Mastodon does. Possibly as part of #349)

I prefer the former option because it seems to be more faithful to the ActivityPub standard, but the ActivityPub recommendation doesn't state that a federating server MAY reject a response without proper Content-Type either, AFAICT.

PoC

None yet.

Impact

For example, an attacker can create a GitHub Gist containing an Activity Streams document with preferredUsername being GitHub, so that they can assume a false handle name of @[email protected].

AT Protocol has (or had?) a similar problem. Mastodon isn't affected by this because it mandates WebFinger support.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits