Summary
A missing authorization check in PeerTube's ActivityPub update handling allows a federated server to submit a video update that appears to belong to another server. Under the affected federation conditions, an attacker may rewrite video metadata, visibility settings, media files, and HLS URLs.
Affected context
The issue occurs in PeerTube deployments that process federated ActivityPub Update activities containing Video objects. The affected processing path does not sufficiently verify that the activity actor is authorized to update the host associated with the video's identifier, allowing malicious federation participants to target content managed by another server.
Exploit preconditions
- Attack surface: ActivityPub federation and inbound video update processing
- Required access: Control of, or participation through, a malicious federated server
- Trigger point: Processing an Update activity containing a Video object
- Why exploitation is possible: The actor identity is not adequately authorized against the host named in the video object's identifier
Why this happens
The vulnerability results from an authorization decision that trusts the relationship between an ActivityPub actor and a video identifier without verifying ownership or update authority. This is an instance of CWE-863: Incorrect Authorization, in which a system permits an actor to perform an operation without correctly establishing that the actor has the required privileges over the target resource.
Potential impact
- An attacker may alter metadata for videos managed by another server
- Video visibility or access settings could be changed without authorization
- Media file references may be replaced or redirected
- HLS URLs could be modified, disrupting playback or directing users to attacker-controlled content
- Federated content integrity and trust may be undermined
General mitigation guidance
Mitigation generally focuses on making authorization explicit for every federated update and treating remote actor claims as untrusted input.
Defensive patterns include:
- Verify that the authenticated or cryptographically validated actor is authorized for the target video's origin and identifier
- Bind update permissions to canonical resource ownership rather than user-controlled fields
- Reject updates when actor, host, and resource relationships cannot be established unambiguously
- Validate media and playback URLs against trusted ownership and federation policies
- Apply least privilege to federation processing and isolate content-management operations
- Use secure-by-default policies that deny cross-origin modifications unless an explicit trust relationship exists
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review checks for authorization decisions based only on object fields or remote claims
- Review of ActivityPub handlers to confirm actor, resource owner, and origin are consistently correlated
- Tests that submit cross-origin updates and verify that unauthorized resources remain unchanged
- Monitoring for unexpected changes to video metadata, visibility, media references, or HLS endpoints
- Policy enforcement requiring authorization checks before applying federated state changes
- Automated security review tools that flag missing object-level authorization controls

