Directus's S3 assets become unavailable after a burst of malformed transformations
directus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @directus/storage-driver-s3 npm |
|
|
| directus npm |
|
|
directus
| Product | Affected | Fixed in |
|---|---|---|
| @directus/storage-driver-s3 npm |
|
|
| directus npm |
|
|
Directus is a real-time API and App dashboard for managing SQL database content. The `@directus/storage-driver-s3` package starting in version 9.22.0 and prior to version 12.0.1, corresponding to Directus starting in version 9.22.0 and prior to 11.5.0, is vulnerable to asset unavailability after a burst of malformed transformations. When making many malformed transformation requests at once, at some point, all assets are served as 403. This causes denial of assets for all policies of Directus, including Admin and Public. Version 12.0.1 of the `@directus/storage-driver-s3` package, corresponding to version 11.5.0 of Directus, fixes the issue.
From the CVE record · GitHub_M
The Directus S3 storage driver can make assets unavailable after a burst of malformed transformation requests. When many such requests are made at once, all assets may be served as 403, including those under Admin and Public policies. The input does not specify authentication requirements or user interaction.
Teams running Directus versions >=9.22.0 <11.5.0 or @directus/storage-driver-s3 versions >=9.22.0 <12.0.1 should check their deployments.