{"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-24753 exists.","fix":"Upgrade bref/bref to 2.1.13 or later.","what":"CVE-2024-24753 is a medium-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-24753 and fix it if it is affected.\n\nWhat it is: CVE-2024-24753 is a medium-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-24753 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-24753/ (Markdown: https://insights.sbomify.com/CVE-2024-24753/index.md)","id":"CVE-2024-24753","markdown":"https://insights.sbomify.com/CVE-2024-24753/index.md","name":"CVE-2024-24753","record":{"aliases":["GHSA-99f9-gv72-fw9r"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Serverless PHP library","requires_auth":"none","summary":"Bref library drops duplicate security headers, allowing attackers to bypass protections like Content-Security-Policy in AWS Lambda applications.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bref","vendor":"mnapoli"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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 in combination with an API Gateway with the v2 format, it does not handle multiple values headers. If PHP generates a response with two headers having the same key but different values only the latest one is kept. If an application relies on multiple headers with the same key being set for security reasons, then Bref would lower the application security. For example, if an application sets multiple `Content-Security-Policy` headers, then Bref would just reflect the latest one. 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 Multiple Value Headers Not Supported in ApiGatewayFormatV2","id":"CVE-2024-24753","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Bref Body Parsing Inconsistency in Event-Driven Functions","id":"CVE-2024-24754"},"packages":[{"ecosystem":"Packagist","fixed":["2.1.13"],"introduced":["0"],"last_affected":[],"package":"bref/bref","purl":null,"source":"GHSA-99f9-gv72-fw9r"},{"ecosystem":"Packagist","fixed":["2.1.13"],"introduced":["0"],"last_affected":[],"package":"bref/bref","purl":"pkg:composer/bref/bref","source":"GHSA-99f9-gv72-fw9r"}],"prev":{"headline":"Bref Uploaded Files Not Deleted in Event-Driven Functions","id":"CVE-2024-24752"},"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":3.7,"headline":"Bref Body Parsing Inconsistency in Event-Driven Functions","id":"CVE-2024-24754","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-06-17","vendors":["brefphp"]},"summary":"Bref library drops duplicate security headers, allowing attackers to bypass protections like Content-Security-Policy in AWS Lambda applications.","url":"https://insights.sbomify.com/CVE-2024-24753/"}