Asset denial via unconsumed S3 HEAD streams
Published Mar 26, 2025 · Updated Mar 26, 2025
Resource exhaustion in Directus allows remote attackers to interrupt S3-backed asset access by sending bursts of HEAD requests. The S3 storage driver's HEAD path obtains object streams without consuming them, leaving NodeHttpHandler Agent sockets occupied until its pool is exhausted. The public asset route requires no authentication, but the condition requires S3-backed storage and sustained parallel requests; all asset policies then receive HTTP 403 responses.
Summary
What happened
Resource exhaustion in Directus allows remote attackers to interrupt S3-backed asset access by sending bursts of HEAD requests. The S3 storage driver's HEAD path obtains object streams without consuming them, leaving NodeHttpHandler Agent sockets occupied until its pool is exhausted. The public asset route requires no authentication, but the condition requires S3-backed storage and sustained parallel requests; all asset policies then receive HTTP 403 responses.
The record
- CVE
- CVE-2025-30350
- Published
- Mar 26, 2025
- Updated
- Mar 26, 2025
- Vendor
- Directus
- Product
- Directus
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2025CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 9.22.0, < 11.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory HEAD-request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo