Directus's S3 assets become unavailable after a burst of HEAD requests
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 HEAD requests. Some tools use Directus to sync content and assets, and some of those tools use the HEAD method to check the existence of files. When making many HEAD requests at once, at some point, all assets are eventually 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
Affected versions of Directus and its S3 storage driver can stop serving assets after a burst of concurrent HEAD requests. Assets are then returned as 403 for all policies, including Admin and Public. The input does not specify whether authentication is needed or user interaction is required.
Check deployments running Directus >=9.22 and <11.5.0 or @directus/storage-driver-s3 >=9.22.0 and <12.0.1.