164 lines
7.8 KiB
JSON
164 lines
7.8 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.2",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2026-111181",
|
|
"assignerOrgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "openjs",
|
|
"dateReserved": "2026-10-15T17:35:18.184Z",
|
|
"datePublished": "2026-10-22T14:29:56.577Z",
|
|
"dateUpdated": "2026-10-22T19:00:31.729Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
|
|
"shortName": "openjs",
|
|
"dateUpdated": "2026-10-22T14:29:56.577Z"
|
|
},
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.",
|
|
"supportingMedia": [
|
|
{
|
|
"type": "text/html",
|
|
"base64": false,
|
|
"value": "body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created."
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"affected": [
|
|
{
|
|
"vendor": "body-parser",
|
|
"product": "body-parser",
|
|
"defaultStatus": "unaffected",
|
|
"versions": [
|
|
{
|
|
"versionType": "semver",
|
|
"status": "affected",
|
|
"version": "2.0.0",
|
|
"lessThan": "2.4.0"
|
|
},
|
|
{
|
|
"versionType": "semver",
|
|
"status": "unaffected",
|
|
"version": "2.4.0"
|
|
},
|
|
{
|
|
"versionType": "semver",
|
|
"status": "affected",
|
|
"version": "0",
|
|
"lessThan": "1.20.9"
|
|
},
|
|
{
|
|
"versionType": "semver",
|
|
"status": "unaffected",
|
|
"version": "1.20.9"
|
|
}
|
|
],
|
|
"packageURL": "pkg:npm/body-parser"
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828"
|
|
},
|
|
{
|
|
"url": "https://cna.openjsf.org/security-advisories.html"
|
|
}
|
|
],
|
|
"credits": [
|
|
{
|
|
"lang": "en",
|
|
"type": "reporter",
|
|
"value": "blue2cat"
|
|
},
|
|
{
|
|
"lang": "en",
|
|
"type": "remediation developer",
|
|
"value": "UlisesGascon"
|
|
},
|
|
{
|
|
"lang": "en",
|
|
"type": "remediation developer",
|
|
"value": "bjohansebas"
|
|
},
|
|
{
|
|
"lang": "en",
|
|
"type": "remediation reviewer",
|
|
"value": "Phillip9587"
|
|
}
|
|
],
|
|
"title": "body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body",
|
|
"metrics": [
|
|
{
|
|
"format": "CVSS",
|
|
"cvssV3_1": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
|
|
"baseScore": 7.5,
|
|
"baseSeverity": "HIGH"
|
|
},
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "GENERAL"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"cweId": "CWE-248",
|
|
"lang": "en",
|
|
"description": "CWE-248: Uncaught Exception",
|
|
"type": "CWE"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"x_generator": {
|
|
"engine": "cve-kit 1.0.0"
|
|
}
|
|
},
|
|
"adp": [
|
|
{
|
|
"metrics": [
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"id": "CVE-2026-111181",
|
|
"role": "CISA Coordinator",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "yes"
|
|
},
|
|
{
|
|
"Technical Impact": "partial"
|
|
}
|
|
],
|
|
"version": "2.0.3",
|
|
"timestamp": "2026-10-22T18:26:41.855566Z"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2026-10-22T19:00:31.729Z"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
} |