Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints
payloadcms payload
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @payloadcms/storage-azure npm |
|
|
| @payloadcms/storage-gcs npm |
|
|
| @payloadcms/storage-r2 npm |
payloadcms payload
| Product | Affected | Fixed in |
|---|---|---|
| @payloadcms/storage-azure npm |
|
|
| @payloadcms/storage-gcs npm |
|
|
| @payloadcms/storage-r2 npm |
< 3.78.0
|
| @payloadcms/storage-s3 npm |
|
|
Payload is a free and open source headless content management system. Prior to version 3.78.0 in @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, and @payloadcms/storage-s3, the client-upload signed-URL endpoints for S3, GCS, Azure, and R2 did not properly sanitize filenames. An attacker could craft filenames to escape the intended storage location. This issue has been patched in version 3.78.0 for @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, and @payloadcms/storage-s3.
From the CVE record · GitHub_M
Before version 3.78.0, the client-upload signed-URL endpoints in Payload's Azure, GCS, R2, and S3 storage packages did not properly sanitize filenames. An attacker could craft a filename that escapes the intended storage location. The input does not specify whether authentication or user interaction is required.
Check deployments using @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, or @payloadcms/storage-s3 before version 3.78.0.