Bref vulnerable to Body Parsing Inconsistency in Event-Driven Functions

Exploitation

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

CVSS

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

EPSS

• CVE-2024-24754: 0.62% estimated exploitation activity in the next 30 days; percentile 49.67 (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:130-168 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 its content added in the $files or $parsedBody arrays. To do that, the following method is called with as first argument the result array ($files or $parsedBody), as second argument the part name, and as third argument the part content: The conversion process produces a different output compared to the one of plain PHP when keys ending with and open square bracket ([) are used. Let's take for example the following part: In plain PHP it would be converted to Array( [key0] = Array ( [key1] = Array ( [key2] = value) ) ), while in Bref it would be converted to Array( [key0] = Array ( [key1] = Array ( [key2] = ) ) [key0[key1][key2][] = value ). Impact Based on the application…

Published by the source

1 Feb 2024, 22:47 UTC

Last modified by the source

1 Feb 2024, 22:47 UTC

Source last checked

26 Oct 2026, 14:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-82vx-mm6r-gg8w

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

# Patch Next advisory brief: CVE-2024-24754

Advisory: Bref vulnerable to Body Parsing Inconsistency in Event-Driven Functions
IDs: CVE-2024-24754, GHSA-82vx-mm6r-gg8w
Record: https://patchnext.com/advisories/cve-2024-24754 (revision 1, source checked 26 Oct 2026, 14:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
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-82vx-mm6r-gg8w (GitHub-reviewed advisory GHSA-82vx-mm6r-gg8w lists affected ranges: Packagist bref/bref >=0 <2.1.13)

Commands are suggestions: review each one before running it.