Bref's Uploaded Files Not Deleted in Event-Driven Functions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2024-24752: 0.75% estimated exploitation activity in the next 30 days; percentile 54.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impacted Resources bref/src/Event/Http/Psr7Bridge.php:94-125 Description 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 brefupload. The function implementing the logic follows: The flow mimics what plain PHP does but it does not delete the temporary files when the request has been processed. Impact An attacker could fill the Lambda instance disk by performing multiple MultiPart requests containing files. The attack has the following requirements and limitations: - The Lambda should use the Event-Driven Function runtime. - The Lambda should use the RequestHandlerInterface handler. - The Lambda should implement at least an endpoint accepting POST requests. - The attacker can send requests up…

Published by the source

1 Feb 2024, 20:53 UTC

Last modified by the source

17 Oct 2024, 19:47 UTC

Source last checked

26 Oct 2026, 14:28 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x4hh-frx8-98r5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-24752

Advisory: Bref's Uploaded Files Not Deleted in Event-Driven Functions
IDs: CVE-2024-24752, GHSA-x4hh-frx8-98r5
Record: https://patchnext.com/advisories/cve-2024-24752 (revision 1, source checked 26 Oct 2026, 14:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: bref/bref 2.1.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist bref/bref: affected < 2.1.13; fixed in 2.1.13

## Suggested inspection (read-only)
- Packagist bref/bref: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on bref/bref.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x4hh-frx8-98r5 (GitHub-reviewed advisory GHSA-x4hh-frx8-98r5 lists affected ranges: Packagist bref/bref >=0 <2.1.13)

Commands are suggestions: review each one before running it.