Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

io.apiman:apiman-distro-vertx

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.1MavenPublished

    Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue

    GHSA-q2fj-6h62-59m2

    Affected
    • Maven io.apiman:apiman-distro-vertx < 3.0.0.Final
    Fixed in
    3.0.0.Final· Vendor fix available
    Issue
    Impact If you are using the Apiman Vert.x Gateway prior to Apiman 3.0.0.Final, a connection caching issue in Hazelcast could allow an unauthenticated, remote attacker to access and manipulate data in the cluster with another authenticated connection's identity. Hazelcast is a transitive dependency of the Apiman Vert.x Gateway. The precise risk is difficult to quantify at this juncture as plugins deployed by users may make use of Hazelcast in a different manner to the main Apiman codebase. If any of your custom Apiman plugins specify Hazelcast dependencies, you should also bump these versions. Hint: an easy way to track Apiman dependency versions is to use apiman-parent. If you use the Apiman Tomcat or WildFly Gateway this does not affect you. Patches Upgrade to Apiman 3.0.0.Final or later. If you are using an older version of Apiman and need to remain on that version, contact to your Apiman support provider for advice/long-term support. Workarounds None (other than doing your own…

    Recommended action: Upgrade to 3.0.0.Final or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →