# GHSA-q2fj-6h62-59m2: Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue

> Unauthenticated remote attackers can access and manipulate cluster data by exploiting a connection caching flaw in the transitive Hazelcast dependency.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2022

## What is GHSA-q2fj-6h62-59m2?

GHSA-q2fj-6h62-59m2 is an authentication bypass vulnerability in io.apiman:apiman-distro-vertx, published on 30 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

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

## Which versions are affected by GHSA-q2fj-6h62-59m2?

4 open source packages ship an affected version, including io.apiman:apiman-distro-vertx and io.apiman:apiman-gateway-platforms-vertx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.apiman:apiman-distro-vertx` | Maven | All versions | 3.0.0.Final |
| `io.apiman:apiman-distro-vertx` | Maven | All versions | 3.0.0.Final |
| `io.apiman:apiman-gateway-platforms-vertx` | Maven | All versions | 3.0.0.Final |
| `io.apiman:apiman-gateway-platforms-vertx` | Maven | All versions | 3.0.0.Final |

## How do I fix GHSA-q2fj-6h62-59m2?

Upgrade io.apiman:apiman-distro-vertx to 3.0.0.Final or later.

## Is GHSA-q2fj-6h62-59m2 being exploited?

There is no known exploitation of GHSA-q2fj-6h62-59m2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q2fj-6h62-59m2 and fix it if it is affected.

What it is: GHSA-q2fj-6h62-59m2 is an authentication bypass vulnerability in io.apiman:apiman-distro-vertx, published on 30 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-q2fj-6h62-59m2 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.apiman:apiman-distro-vertx (Maven): affected all versions; fixed in 3.0.0.Final
- io.apiman:apiman-distro-vertx (Maven): affected all versions; fixed in 3.0.0.Final
- io.apiman:apiman-gateway-platforms-vertx (Maven): affected all versions; fixed in 3.0.0.Final
- io.apiman:apiman-gateway-platforms-vertx (Maven): affected all versions; fixed in 3.0.0.Final

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-q2fj-6h62-59m2/ (Markdown: https://insights.sbomify.com/GHSA-q2fj-6h62-59m2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q2fj-6h62-59m2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q2fj-6h62-59m2/
Summaries are generated and may contain mistakes; the official description above is the record.