Skip to content

fix: check PutObjectTagging/LegalHold/Retention permissions on PutObject and CreateMultipartUpload#2011

Open
niksis02 wants to merge 1 commit intomainfrom
sis/putobject-meta-property-permissions
Open

fix: check PutObjectTagging/LegalHold/Retention permissions on PutObject and CreateMultipartUpload#2011
niksis02 wants to merge 1 commit intomainfrom
sis/putobject-meta-property-permissions

Conversation

@niksis02
Copy link
Copy Markdown
Contributor

@niksis02 niksis02 commented Apr 2, 2026

Fixes #1986

When a client includes tagging, legal hold, or retention headers in a PutObject or CreateMultipartUpload request, the corresponding bucket policy permissions must be verified in addition to s3:PutObject:

X-Amz-Tagging - s3:PutObjectTagging
X-Amz-Object-Lock-Legal-Hold - s3:PutObjectLegalHold X-Amz-Object-Lock-Mode - s3:PutObjectRetention

Previously, only s3:PutObject was checked, allowing users to set tagging, legal hold, and retention without having the required permissions. Now each action permission is check, if user tries to add them.

…ect and CreateMultipartUpload

Fixes #1986

When a client includes tagging, legal hold, or retention headers in a PutObject or CreateMultipartUpload request, the corresponding bucket policy permissions must be verified in addition to s3:PutObject:

`X-Amz-Tagging` - `s3:PutObjectTagging`
`X-Amz-Object-Lock-Legal-Hold` - `s3:PutObjectLegalHold`
`X-Amz-Object-Lock-Mode` - `s3:PutObjectRetention`

Previously, only s3:PutObject was checked, allowing users to set tagging, legal hold, and retention without having the required permissions. Now each action permission is check, if user tries to add them.
@niksis02 niksis02 self-assigned this Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] - PutObject/CreateMultipartUpload permissions

1 participant