# CVE-2024-24752: Bref Uploaded Files Not Deleted in Event-Driven Functions

> Attackers can exhaust Lambda disk space by sending multiple multipart requests, causing denial of service in Bref serverless PHP applications.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Feb 2024
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-x4hh-frx8-98r5

## What is CVE-2024-24752?

CVE-2024-24752 is a medium-severity denial of service vulnerability in brefphp bref, published on 1 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bref enable serverless PHP on AWS Lambda. When Bref is used with the Event-Driven Function runtime and the handler is a `RequestHandlerInterface`, then the Lambda event is converted to a PSR7 object. During the conversion process, if the request is a MultiPart, each part is parsed and for each which contains a file, it is extracted and saved in `/tmp` with a random filename starting with `bref_upload_`. The flow mimics what plain PHP does but it does not delete the temporary files when the request has been processed. An attacker could fill the Lambda instance disk by performing multiple MultiPart requests containing files. This vulnerability is patched in 2.1.13.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-24752?

2 open source packages ship an affected version, including bref/bref. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bref/bref` | Packagist | All versions | 2.1.13 |
| `bref/bref` | Packagist | All versions | 2.1.13 |

Products: Mnapoli Bref.

## How do I fix CVE-2024-24752?

Upgrade bref/bref to 2.1.13 or later.

## Is CVE-2024-24752 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24752 exists.

## Other vulnerabilities in brefphp bref

- [CVE-2024-29186](https://insights.sbomify.com/CVE-2024-29186/): Slow String Operations via MultiPart Requests in Event-Driven Functions (medium 5.3)
- [CVE-2024-24753](https://insights.sbomify.com/CVE-2024-24753/): Bref Multiple Value Headers Not Supported in ApiGatewayFormatV2 (medium 4.8)
- [CVE-2024-24754](https://insights.sbomify.com/CVE-2024-24754/): Bref Body Parsing Inconsistency in Event-Driven Functions (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24752 and fix it if it is affected.

What it is: CVE-2024-24752 is a medium-severity denial of service vulnerability in brefphp bref, published on 1 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24752 exists.

Affected packages and fixed versions:
- bref/bref (Packagist): affected all versions; fixed in 2.1.13
- bref/bref (Packagist): affected all versions; fixed in 2.1.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24752/ (Markdown: https://insights.sbomify.com/CVE-2024-24752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24752
- OSV: https://osv.dev/vulnerability/CVE-2024-24752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24752/
Summaries are generated and may contain mistakes; the official description above is the record.