NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Apiman Vert.x Gateway has Transitive Hazelcast connection caching issueGHSA-q2fj-6h62-59m2

HIGH

GHSA-q2fj-6h62-59m2 is a high-severity (CVSS 8.1) vulnerability in io.apiman:apiman-gateway-platforms-vertx. A fix is available for io.apiman:apiman-gateway-platforms-vertx — see the affected versions and patch details below.

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
☕io.apiman:apiman-gateway-platforms-vertx☕io.apiman:apiman-distro-vertx

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 build).

References

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.apiman:apiman-gateway-platforms-vertxall versions3.0.0.Finalio.apiman:apiman-gateway-platforms-vertx:3.0.0.Final
☕Mavenio.apiman:apiman-distro-vertxall versions3.0.0.Finalio.apiman:apiman-distro-vertx:3.0.0.Final

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.apiman:apiman-gateway-platforms-vertx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.apiman:apiman-gateway-platforms-vertx to 3.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q2fj-6h62-59m2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 thes
O3 Security · Impact-Aware SCA

Is GHSA-q2fj-6h62-59m2 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apiman Vert.x Gateway has Transitive Hazelcast…