Skip to content
Fencer Intel
high 8.1

GHSA-q2fj-6h62-59m2 json

Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue

published 3y ago modified last yr.

cvss
8.1
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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

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

Patch / fix

  • maven io.apiman:apiman-gateway-platforms-vertx 3.0.0.Final
  • maven io.apiman:apiman-distro-vertx 3.0.0.Final

Is GHSA-q2fj-6h62-59m2 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven io.apiman:apiman-gateway-platforms-vertx
<3.0.0.Final
3.0.0.Final
maven io.apiman:apiman-distro-vertx
<3.0.0.Final
3.0.0.Final

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.