Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an invalid limit option value such as an unparseable string or NaN, bytes.parse returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service. Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement, while null and undefined continue to fall back to the default limit of 100kb. Workarounds: Validate the limit value before passing it to body-parser. For example, parse the value at startup and reject any configuration where the result is null or a non-finite number.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LOpenjsf Body Parser
APPOpenjsf< 1.20.62.0.0 – 2.3.0 (excl.)
Related vulnerabilities
body-parser is Node.js body parsing middleware. body-parser <1.20.3 is vulnerable to denial of service when ur...
WebdriverIO: command injection w orkiestracji testów prowadzący do RCE
fast-uri accepts a host that contains an unbalanced or misplaced authority bracket without reporting an error....
fast-uri serializes the port component of a URI without validating it. When recomposing the authority, the use...
fast-uri is a URI parser for Node.js. It decodes percent escapes in a hostname during parsing and then decodes...