Bref Multiple Value Headers Not Supported in ApiGatewayFormatV2
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-24753
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 12:03 UTC · Revision 1
Source evidence
Bref Multiple Value Headers Not Supported in ApiGatewayFormatV2
core-osv · Original sourcePublished 1 Feb 2024, 16:09 UTC
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.
osv:CVE-2024-24753
Complete source record
{
"id": "799b1ac09a092002cdf42fd0340a944c77731cc7cb666128471a935c2e7790b8",
"url": "https://osv.dev/vulnerability/CVE-2024-24753",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bref Multiple Value Headers Not Supported in ApiGatewayFormatV2",
"summary": "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.",
"evidence": "osv:CVE-2024-24753",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2024-24753",
"aliases": [
"CVE-2024-24753",
"GHSA-99f9-gv72-fw9r"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/brefphp/bref",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "535ad5f035d16892dbccbb785be2333f987a81e3"
},
{
"fixed": "f834027aaf88b3885f4aa8edf6944ae920daf2dc"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:mnapoli:bref:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "2.1.13"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "f834027aaf88b3885f4aa8edf6944ae920daf2dc"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"2.1.12",
"2.1.11",
"2.1.10",
"2.1.9",
"2.1.8",
"2.1.7",
"2.1.6",
"2.1.5",
"2.1.4",
"2.1.3",
"2.1.2",
"2.1.1",
"2.1.0",
"2.0.11",
"2.0.10",
"2.0.8",
"2.0.9",
"2.0.7",
"2.0.6",
"2.0.5",
"2.0.4",
"2.0.3",
"2.0.2",
"2.0.1",
"2.0.0",
"1.7.24",
"1.7.23",
"1.7.22",
"1.7.21",
"1.7.20",
"1.7.19",
"1.7.18",
"1.7.17",
"1.7.16",
"1.7.15",
"1.7.14",
"1.7.13",
"1.7.12",
"1.7.11",
"1.7.10",
"1.7.9",
"1.7.8",
"1.7.7",
"1.7.6",
"1.7.5",
"1.7.4",
"1.7.3",
"1.7.2",
"1.7.1",
"1.7.0",
"1.6.0",
"1.5.8",
"1.5.7",
"1.5.6",
"1.5.5",
"1.5.4",
"1.5.3",
"1.5.2",
"1.5.1",
"1.5.0",
"1.4.2",
"1.4.1",
"1.4.0",
"1.3.6",
"1.3.5",
"1.3.4",
"1.3.3",
"1.3.2",
"1.3.1",
"1.3.0",
"1.2.14",
"1.2.13",
"1.2.12",
"1.2.11",
"1.2.10",
"1.2.9",
"1.2.8",
"1.2.7",
"1.2.6",
"1.2.5",
"1.2.4",
"1.2.3",
"1.2.2",
"1.2.1",
"1.2.0",
"1.1.4",
"1.1.3",
"1.1.2",
"1.1.1",
"1.1.0",
"1.0.2",
"1.0.1",
"1.0.0",
"0.5.33",
"1.0.0-beta1",
"0.5.32",
"0.5.31",
"0.5.30",
"0.5.14-beta1",
"0.5.29",
"0.5.28",
"0.5.27",
"0.5.26",
"0.5.25",
"0.5.24",
"0.5.23",
"0.5.22",
"0.5.21",
"0.5.20",
"0.5.19",
"0.5.18",
"0.5.17",
"0.5.16",
"0.5.15",
"0.5.14",
"0.5.14-beta2",
"0.5.13",
"0.5.12",
"0.5.3",
"0.5.2",
"0.5.1",
"0.5.0",
"0.5.0-beta1",
"0.4.1",
"0.4.0",
"0.3.9",
"0.3.5",
"0.3.8",
"0.3.7",
"0.3.6",
"0.3.4",
"0.3.3",
"0.3.2",
"0.3.1",
"0.3.0",
"0.2.37",
"0.2.36",
"0.2.35",
"0.2.34",
"0.2.33",
"0.2.32",
"0.2.31",
"0.2.30",
"0.2.29",
"0.2.28",
"0.2.27",
"0.2.26",
"0.2.20",
"0.2.19",
"0.2.18",
"0.2.17",
"0.2.16",
"0.2.15",
"0.2.14",
"0.2.13",
"0.2.12",
"0.2.11",
"0.2.10",
"0.2.9",
"0.2.8",
"0.2.7",
"0.2.6",
"0.2.5",
"0.2.4",
"0.2.3",
"0.2.2",
"0.2.1",
"0.2.0",
"0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-24753.json"
}
}
],
"modified": "2026-10-28T02:30:50.897939097Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/24xxx/CVE-2024-24753.json",
"https://github.com/brefphp/bref/security/advisories/GHSA-99f9-gv72-fw9r",
"https://nvd.nist.gov/vuln/detail/CVE-2024-24753",
"https://github.com/brefphp/bref/commit/f834027aaf88b3885f4aa8edf6944ae920daf2dc"
],
"provider_metadata": {
"cwe_ids": [
"CWE-436"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/24xxx/CVE-2024-24753.json"
}
},
"related_cves": [
{
"value": "CVE-2024-24753",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 519221,
"published_at": "2024-02-01T16:09:55.328+00:00"
}