Vulnerabilities

 2 via 6 paths

Dependencies

 26

Source

 GitHub

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 1
  • 1
Status
  • 2
  • 0
  • 0

high severity
new

Origin Validation Error

  • Vulnerable module: io.vertx:vertx-core
  • Introduced through: io.vertx:vertx-core@4.5.24, io.vertx:vertx-web@4.5.24 and others

Detailed paths

  • Introduced through: Stwissel/vertx-sfdc-platformevents@Stwissel/vertx-sfdc-platformevents › io.vertx:vertx-core@4.5.24
    Remediation: Upgrade to io.vertx:vertx-core@4.5.30.
  • Introduced through: Stwissel/vertx-sfdc-platformevents@Stwissel/vertx-sfdc-platformevents › io.vertx:vertx-web@4.5.24 › io.vertx:vertx-bridge-common@4.5.24 › io.vertx:vertx-core@4.5.24
    Remediation: Upgrade to io.vertx:vertx-web@4.5.30.
  • Introduced through: Stwissel/vertx-sfdc-platformevents@Stwissel/vertx-sfdc-platformevents › io.vertx:vertx-web-client@4.5.24 › io.vertx:vertx-uri-template@4.5.24 › io.vertx:vertx-core@4.5.24
    Remediation: Upgrade to io.vertx:vertx-web-client@4.5.30.

Overview

io.vertx:vertx-core is a tool-kit for building reactive applications on the JVM.

Affected versions of this package are vulnerable to Origin Validation Error in the DefaultRedirectHandler, which forwards request headers, including Authorization, Cookie, Proxy-Authorization, and custom headers such as X-API-Token, across cross-origin redirects without comparing the scheme, host, and port of the origin. An attacker controlling a redirect destination can capture bearer tokens, basic-auth credentials, session cookies, and API keys attached to the original request by returning a redirect to a host they control. This requires the attacker to cause a Vert.x HttpClient request to be redirected to that host, such as through a webhook dispatcher or image proxy that follows redirects.

Workaround

This vulnerability can be avoided by disabling automatic redirect following on the HttpClient (for example setFollowRedirects(false)) for requests that carry credentials, so credential headers are not replayed to a redirect target.

Remediation

Upgrade io.vertx:vertx-core to version 4.5.30, 5.1.5 or higher.

References

Origin Validation Error vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: io.vertx:vertx-core
  • Introduced through: io.vertx:vertx-core@4.5.24, io.vertx:vertx-web@4.5.24 and others

Detailed paths

  • Introduced through: Stwissel/vertx-sfdc-platformevents@Stwissel/vertx-sfdc-platformevents › io.vertx:vertx-core@4.5.24
    Remediation: Upgrade to io.vertx:vertx-core@4.5.27.
  • Introduced through: Stwissel/vertx-sfdc-platformevents@Stwissel/vertx-sfdc-platformevents › io.vertx:vertx-web@4.5.24 › io.vertx:vertx-bridge-common@4.5.24 › io.vertx:vertx-core@4.5.24
    Remediation: Upgrade to io.vertx:vertx-web@4.5.27.
  • Introduced through: Stwissel/vertx-sfdc-platformevents@Stwissel/vertx-sfdc-platformevents › io.vertx:vertx-web-client@4.5.24 › io.vertx:vertx-uri-template@4.5.24 › io.vertx:vertx-core@4.5.24
    Remediation: Upgrade to io.vertx:vertx-web-client@4.5.27.

Overview

io.vertx:vertx-core is a tool-kit for building reactive applications on the JVM.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling during the TLS handshake process, where the SslContext cache can be forced to grow indefinitely. The SSLHelper, SslChannelProvider, and SslContextProvider classes responsible for this caching in different versions all exhibit the same vulnerable behavior. A malicious client can disrupt service by sending a large number of distinct valid SNI names. This is particularly likely when the server has a broad hostname rule such as a wildcard.

Remediation

Upgrade io.vertx:vertx-core to version 4.5.27, 5.0.12 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report