CyberRota Analysis
AI-GeneratedOpenStack Swift versions up to 2.38.0 are vulnerable due to the S3API middleware failing to sanitize control headers in S3 API requests when the s3_acl configuration is set to true. This flaw allows an attacker to manipulate signed PUT requests to perform unauthorized server-side copies of private objects from other tenants, bypassing access controls. Organizations using OpenStack Swift with the non-default s3_acl=true setting should prioritize addressing this vulnerability to prevent potential data breaches.
Original NVD Description
In OpenStack Swift through 2.38.0, the S3API middleware does not sanitize Swift-native control headers (X-Copy-From, X-Copy-From-Account) from S3 API requests when s3_acl=true. An attacker can inject these headers into a signed PUT request targeting their own bucket, causing Swift to perform a server-side copy from another tenant's private object. The source object authorization is bypassed because the S3API middleware has already authorized the request against the destination. The attacker can read any object whose project_id, container name, and object name are known, regardless of the source object's ACLs or ownership. This requires the non-default s3_acl=true configuration.