CyberRota Analysis
AI-GeneratedOpenStack Swift versions up to 2.38.0 are vulnerable due to the S3API middleware's failure to enforce signature validation on certain x-amz-* headers in presigned URL requests. This allows an attacker with access to a presigned PUT URL to exploit the system by injecting an unsigned X-Amz-Copy-Source header, enabling unauthorized server-side object copies from any accessible source object. Organizations utilizing OpenStack Swift with the default s3_acl=false configuration should prioritize addressing this vulnerability to prevent potential data exposure.
Original NVD Description
In OpenStack Swift through 2.38.0, S3API middleware does not enforce that semantic x-amz-* headers are covered by the SigV4 signature on presigned URL requests. An attacker who obtains a presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, causing Swift to perform a server-side copy from an arbitrary source object using the signer's authorization context. The attacker can read any object the signer has access to, provided the target project_id, container name, and object name are known. This affects all deployments using the default s3_acl=false configuration.