Security: MessageAttachment API item GET missing message-ownership check (IDOR) - #8794
Merged
AngelFQC merged 1 commit intoJul 31, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
MessageAttachmentitem GET was gated onis_granted('ROLE_USER')only, so any authenticated user could enumerate the auto-increment attachment ids and read other users' private-message attachment metadata (comment, contentUrl, downloadUrl). The operation is now scoped to the parent message's ownership viais_granted('VIEW', object.getMessage()), reusing the existingMessageVoter(sender/receiver check) exactly as the parentMessageresource already does.Refs GHSA-jf75-vp35-w4mg