Lambda storage exhaustion via undeleted multipart files
Published Feb 1, 2024 · Updated Oct 17, 2024
Resource exhaustion in Bref before 2.1.13 allows remote attackers to fill AWS Lambda storage through multipart uploads. Psr7Bridge writes every multipart file part to a bref_upload_ temporary file but leaves those files behind after request processing. The affected path requires the Event-Driven Function runtime, a RequestHandlerInterface handler, a POST endpoint, and repeated requests to exhaust the default 512 MB temporary disk.
Summary
What happened
Resource exhaustion in Bref before 2.1.13 allows remote attackers to fill AWS Lambda storage through multipart uploads. Psr7Bridge writes every multipart file part to a bref_upload_ temporary file but leaves those files behind after request processing. The affected path requires the Event-Driven Function runtime, a RequestHandlerInterface handler, a POST endpoint, and repeated requests to exhaust the default 512 MB temporary disk.
The record
- CVE
- CVE-2024-24752
- Published
- Feb 1, 2024
- Updated
- Oct 17, 2024
- Vendor
- Bref
- Product
- Bref
- Classifications
- CWE-770, CWE-400, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- Oct 17, 2024Record 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=< 2.1.13
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
- Upstream multipart temporary-file exhaustion 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