GHSA-v422-hmwv-36x6 body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement

• npm body-parser: < 1.20.6 → fixed in 1.20.6 • npm body-parser: >= 2.0.0, < 2.3.0 → fixed in 2.3.0

Impact When body-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. This issue affects applications that pass a programmatically computed or user-configurable value to the `limit` option without validating it first. Patches This issue is fixed in [email protected] and [email protected] via #698. After the fix, invalid `limit` values throw a clear error at parser construction time instead of silently disabling enforcement. `null` and `undefined` continue to fall back to the default limit (`100kb`). Workarounds Validate `limit` before passing it to body-parser. For example, parse the value with `bytes.parse()` at startup and reject any configuration where it returns `null` or a non-finite number. References • #698: fix PR • bytes.js: limit parser