GHSA-Q2FJ-6H62-59M2

Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue

Workarounds

None (other than doing your own build).

References

• https://github.com/advisories/GHSA-c5hg-mr8r-f6jp

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.

GHSA-Q2FJ-6H62-59M2 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.0.Final); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is GHSA-Q2FJ-6H62-59M2? GHSA-Q2FJ-6H62-59M2 is a high-severity security vulnerability in io.apiman:apiman-gateway-platforms-vertx (maven), affecting versions < 3.0.0.Final. It is fixed in 3.0.0.Final.
2. How severe is GHSA-Q2FJ-6H62-59M2? GHSA-Q2FJ-6H62-59M2 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by GHSA-Q2FJ-6H62-59M2?
   • io.apiman:apiman-gateway-platforms-vertx (maven) (versions < 3.0.0.Final)
   • io.apiman:apiman-distro-vertx (maven) (versions < 3.0.0.Final)
4. Is there a fix for GHSA-Q2FJ-6H62-59M2? Yes. GHSA-Q2FJ-6H62-59M2 is fixed in 3.0.0.Final. Upgrade to this version or later.
5. Is GHSA-Q2FJ-6H62-59M2 exploitable, and should I be worried? Whether GHSA-Q2FJ-6H62-59M2 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-Q2FJ-6H62-59M2 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-Q2FJ-6H62-59M2?
   • Upgrade io.apiman:apiman-gateway-platforms-vertx to 3.0.0.Final or later
   • Upgrade io.apiman:apiman-distro-vertx to 3.0.0.Final or later