Medium, CVSS 5.3npmAmendedPublished
Directus's S3 assets become unavailable after a burst of malformed transformations
CVE-2025-30225 · GHSA-j8xj-7jff-46mx
- Affected
- npm @directus/storage-driver-s3 >= 9.22.0, < 12.0.1
- Fixed in
- 12.0.1· Vendor fix available
- Issue
- When making many malformed transformation requests at once, at some point, all assets are being served as 403. Details When I was investigating this issue, I have found that after a burst of malformed asset transformation requests, the amount of sockets held on Agent on NodeHttpHandler was always equal to STORAGECLOUDMAXSOCKETS making it impossible to have new connections causing assets to be inaccessible. After looking into this issue on AWS SDK I found that if the stream is requested, it needs to be consumed otherwise will hang forever. And as can be seen here the stream is not consumed, because sharp will throw an error on the invalid arguments. For example ?height=xyz The timeouts set here had no noticeable effect on tests made. PoC This can be easily reproduced with the following steps: - setup AWS S3 storage - set STORAGECLOUDMAXSOCKETS: "50" (this value is lower than default for easier reproduction) - upload a file to your project - run this file (Replace the the file…
Recommended action: Upgrade to 12.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.