org.webjars.npm:multiparty@4.2.2

  • latest version

    4.2.2

  • first published

    8 years ago

  • latest version published

    5 years ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the org.webjars.npm:multiparty package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Uncaught Exception

    org.webjars.npm:multiparty is a multipart/form-data parser which supports streaming

    Affected versions of this package are vulnerable to Uncaught Exception through the parsing of multipart/form-data requests containing field names that collide with inherited Object.prototype properties. An attacker can cause the process to crash by sending specially crafted requests that trigger an uncaught exception.

    How to fix Uncaught Exception?

    A fix was pushed into the master branch but not yet published.

    [0,)
    • H
    Regular Expression Denial of Service (ReDoS)

    org.webjars.npm:multiparty is a multipart/form-data parser which supports streaming

    Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the Content-Disposition filename parameter parsing. An attacker can cause excessive resource consumption and block the event loop by submitting a multipart upload with a specially crafted long header value that triggers regular expression backtracking.

    How to fix Regular Expression Denial of Service (ReDoS)?

    A fix was pushed into the master branch but not yet published.

    [0,)
    • H
    Improper Handling of Exceptional Conditions

    org.webjars.npm:multiparty is a multipart/form-data parser which supports streaming

    Affected versions of this package are vulnerable to Improper Handling of Exceptional Conditions via the filename* parameter parsing in multipart form-data requests. An attacker can cause the process to crash by sending a request with a malformed percent-encoding in the filename* parameter, which triggers an uncaught exception.

    How to fix Improper Handling of Exceptional Conditions?

    A fix was pushed into the master branch but not yet published.

    [0,)