{"answers":{"affected":"2 open source packages ship an affected version, including bref/bref. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24754 exists.","fix":"Upgrade bref/bref to 2.1.13 or later.","what":"CVE-2024-24754 is a low-severity vulnerability in brefphp bref, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-24754 and fix it if it is affected.\n\nWhat it is: CVE-2024-24754 is a low-severity vulnerability in brefphp bref, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24754 exists.\n\nAffected packages and fixed versions:\n- bref/bref (Packagist): affected all versions; fixed in 2.1.13\n- bref/bref (Packagist): affected all versions; fixed in 2.1.13\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-24754/ (Markdown: https://insights.sbomify.com/CVE-2024-24754/index.md)","id":"CVE-2024-24754","markdown":"https://insights.sbomify.com/CVE-2024-24754/index.md","name":"CVE-2024-24754","record":{"aliases":["GHSA-82vx-mm6r-gg8w"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Serverless PHP library","requires_auth":"none","summary":"Inconsistent multipart body parsing in Bref can lead to application logic errors or undefined behaviors in serverless PHP functions.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bref","vendor":"mnapoli"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"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 its content added in the `$files` or `$parsedBody` arrays. The conversion process produces a different output compared to the one of plain PHP when keys ending with and open square bracket ([) are used. Based on the application logic the difference in the body parsing might lead to vulnerabilities and/or undefined behaviors. This vulnerability is patched in 2.1.13.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Bref Body Parsing Inconsistency in Event-Driven Functions","id":"CVE-2024-24754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"other","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"discourse-group-membership-ip-block is exposing potentially sensitive custom fields","id":"CVE-2024-24755"},"packages":[{"ecosystem":"Packagist","fixed":["2.1.13"],"introduced":["0"],"last_affected":[],"package":"bref/bref","purl":null,"source":"GHSA-82vx-mm6r-gg8w"},{"ecosystem":"Packagist","fixed":["2.1.13"],"introduced":["0"],"last_affected":[],"package":"bref/bref","purl":"pkg:composer/bref/bref","source":"GHSA-82vx-mm6r-gg8w"}],"prev":{"headline":"Bref Multiple Value Headers Not Supported in ApiGatewayFormatV2","id":"CVE-2024-24753"},"products":["bref"],"published":"2024-02-01","related":[{"cvss_score":6.5,"headline":"Bref Uploaded Files Not Deleted in Event-Driven Functions","id":"CVE-2024-24752","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":5.3,"headline":"Slow String Operations via MultiPart Requests in Event-Driven Functions","id":"CVE-2024-29186","kev_date_added":null,"published":"2024-03-22"},{"cvss_score":4.8,"headline":"Bref Multiple Value Headers Not Supported in ApiGatewayFormatV2","id":"CVE-2024-24753","kev_date_added":null,"published":"2024-02-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-15","vendors":["brefphp"]},"summary":"Inconsistent multipart body parsing in Bref can lead to application logic errors or undefined behaviors in serverless PHP functions.","url":"https://insights.sbomify.com/CVE-2024-24754/"}