raw-body is vulnerable to Allocation of Resources Without Limits or Throttling
37
Low Risk
raw-body accepts a limit option to cap how many bytes are read from a stream. When limit is set to an unparseable value such as an invalid size string or NaN, parsing yields no usable byte count and size enforcement is skipped. The reader then buffers the full stream without the intended cap, which can exhaust memory or CPU and deny service. The fix rejects invalid limit values with a TypeError instead of silently disabling the limit; limit: null remains the explicit way to disable it.
You are affected if you are using a version that falls within the vulnerable range and your application passes an invalid or unparseable value to the limit option.
raw-body is vulnerable to Allocation of Resources Without Limits or Throttling in versions 0.0.1 - 3.0.2.
Upgrade the raw-body library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant