org.webjars.npm:undici@4.12.2 vulnerabilities

  • latest version

    5.28.3

  • first published

    2 years ago

  • latest version published

    3 months ago

  • licenses detected

  • package manager

Direct Vulnerabilities

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

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • L
Improper Authorization

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Improper Authorization due to improper handling of Proxy-Authorization headers during cross-origin redirects in certain methods. An attacker can exploit this behavior by inducing a victim to make a request that triggers a cross-origin redirect, potentially leaking sensitive information contained in the Proxy-Authorization header.

How to fix Improper Authorization?

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

[0,)
  • L
Improper Access Control

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Improper Access Control due to the integrity option passed to fetch(). An attacker can alter this option, allowing fetch() to accept requests as valid even if they have been tampered with.

How to fix Improper Access Control?

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

[0,)
  • L
Permissive Cross-domain Policy with Untrusted Domains

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Permissive Cross-domain Policy with Untrusted Domains due to not clearing Proxy-Authentication headers on cross-origin redirects. An attacker can intercept the improperly cleared headers.

How to fix Permissive Cross-domain Policy with Untrusted Domains?

Upgrade org.webjars.npm:undici to version 5.28.3 or higher.

[,5.28.3)
  • L
Information Exposure

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Information Exposure during the Cookie headers handling process. An attacker can potentially leak sensitive information to a third-party site or a malicious actor who can control the redirection target (i.e., an open redirector) by exploiting the disconnect between the spec's assumptions and the implementation of fetch.

Note:

This is only exploitable if the attacker can control the redirection target.

How to fix Information Exposure?

Upgrade org.webjars.npm:undici to version 5.27.0 or higher.

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

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the Headers.set() and Headers.append() methods, when untrusted values are passed into the functions. This is due to the inefficient regular expression used to normalize the values in the headerValueNormalize() utility function.

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

Upgrade org.webjars.npm:undici to version 5.20.0 or higher.

[,5.20.0)
  • M
CRLF Injection

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to CRLF Injection due to missing protection for the host HTTP header.

How to fix CRLF Injection?

Upgrade org.webjars.npm:undici to version 5.20.0 or higher.

[,5.20.0)
  • M
CRLF Injection

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to CRLF Injection when using unsanitized input as request headers (for example, inside the content-type header).

How to fix CRLF Injection?

Upgrade org.webjars.npm:undici to version 5.10.0 or higher.

[,5.10.0)
  • M
Server-side Request Forgery (SSRF)

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) when an application takes in unsanitized user input into the path/pathname option of undici.request.

How to fix Server-side Request Forgery (SSRF)?

Upgrade org.webjars.npm:undici to version 5.10.0 or higher.

[,5.10.0)
  • L
Information Exposure

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Information Exposure by not clearing cookie headers upon third party redirect.

Note: This is only exploitable when maxRedirections is changed from its default value of 0.

How to fix Information Exposure?

Upgrade org.webjars.npm:undici to version 5.10.0 or higher.

[,5.10.0)
  • M
CRLF Injection

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to CRLF Injection in lib/core/request.js that allows HTTP requests to be injected via unexpected CRLF (\r\n) sequences in request path, method, and headers received from untrusted sources.

How to fix CRLF Injection?

Upgrade org.webjars.npm:undici to version 5.10.0 or higher.

[,5.10.0)
  • M
Improper Certificate Validation

org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js

Affected versions of this package are vulnerable to Improper Certificate Validation due to Undici.ProxyAgent missing verification of the remote server's certificate, which leads to exposure of all the requests and responses data to the proxy.

How to fix Improper Certificate Validation?

Upgrade org.webjars.npm:undici to version 5.5.1 or higher.

[4.8.2,5.5.1)