{"id":"GHSA-q2fj-6h62-59m2","aliases":[],"status":"published","title":"Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue","description":"### Impact\n\nIf 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.\n\nHazelcast is a transitive dependency of the Apiman Vert.x Gateway.\n\nThe 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.\n\nIf any of your custom Apiman plugins specify Hazelcast dependencies, you should also bump these versions. \n\nHint: an easy way to track Apiman dependency versions is to use `apiman-parent`.\n\nIf you use the Apiman Tomcat or WildFly Gateway this does not affect you.\n\n### Patches\n\nUpgrade to **Apiman 3.0.0.Final or later**.\n\nIf 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.\n\n### Workarounds\n\nNone (other than doing your own build).\n\n### References\n\n* https://github.com/advisories/GHSA-c5hg-mr8r-f6jp","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","from":"ghsa"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2022-12-30T22:13:59Z","modified":"2024-12-02T05:52:25Z","fixes":[{"ecosystem":"Maven","package":"io.apiman:apiman-gateway-platforms-vertx","fixed_in":["3.0.0.Final"],"sources":["ghsa","osv"]},{"ecosystem":"Maven","package":"io.apiman:apiman-distro-vertx","fixed_in":["3.0.0.Final"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"io.apiman:apiman-gateway-platforms-vertx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0.Final"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"io.apiman:apiman-distro-vertx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0.Final"}]}]},{"source":"osv","ecosystem":"Maven","package":"io.apiman:apiman-gateway-platforms-vertx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0.Final"}]}],"versions":["1.0.0.Final","1.0.1.Final","1.1.2.Final","1.1.2.Preview2","1.1.3.CR1","1.1.3.Final","1.1.4.Final","1.1.5.Final"]},{"source":"osv","ecosystem":"Maven","package":"io.apiman:apiman-distro-vertx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0.Final"}]}],"versions":["1.3.0.Final","1.3.1.Final","1.3.2.Final","1.3.3.Final","1.3.4.Final","1.3.5.Final","1.4.0.Final","1.4.1.Final","1.4.2.Final","1.4.3.Final","1.5.0.Final","1.5.1.Final","1.5.2.Final","1.5.3.Final","1.5.4.Final","1.5.5.Final","1.5.6.Final","1.5.7.Final","2.0.0.Final","2.1.1.Final","2.1.2.Final","2.1.3.Final","2.1.4.Final","2.1.5.Final","2.2.0.Final","2.2.1.Final","2.2.2.Final","2.2.3.Final","3.0.0.RC6"]}],"references":[{"url":"https://github.com/apiman/apiman/security/advisories/GHSA-q2fj-6h62-59m2","tags":["web"]},{"url":"https://github.com/advisories/GHSA-c5hg-mr8r-f6jp","tags":["advisory"]},{"url":"https://support.hazelcast.com/s/article/Security-Advisory-for-CVE-2022-36437","tags":["web"]},{"url":"https://github.com/advisories/GHSA-q2fj-6h62-59m2"},{"url":"https://github.com/apiman/apiman","tags":["package"]}],"sources":{"ghsa":[{"id":"GHSA-q2fj-6h62-59m2","title":"Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue","description":"### Impact\n\nIf 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.\n\nHazelcast is a transitive dependency of the Apiman Vert.x Gateway.\n\nThe 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.\n\nIf any of your custom Apiman plugins specify Hazelcast dependencies, you should also bump these versions. \n\nHint: an easy way to track Apiman dependency versions is to use `apiman-parent`.\n\nIf you use the Apiman Tomcat or WildFly Gateway this does not affect you.\n\n### Patches\n\nUpgrade to **Apiman 3.0.0.Final or later**.\n\nIf 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.\n\n### Workarounds\n\nNone (other than doing your own build).\n\n### References\n\n* https://github.com/advisories/GHSA-c5hg-mr8r-f6jp","status":"published","published":"2022-12-30T22:13:59Z","modified":"2023-01-07T05:05:25Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T14:36:01.39976Z"}],"osv":[{"id":"GHSA-q2fj-6h62-59m2","title":"Apiman Vert.x Gateway has Transitive Hazelcast connection caching issue","description":"### Impact\n\nIf 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.\n\nHazelcast is a transitive dependency of the Apiman Vert.x Gateway.\n\nThe 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.\n\nIf any of your custom Apiman plugins specify Hazelcast dependencies, you should also bump these versions. \n\nHint: an easy way to track Apiman dependency versions is to use `apiman-parent`.\n\nIf you use the Apiman Tomcat or WildFly Gateway this does not affect you.\n\n### Patches\n\nUpgrade to **Apiman 3.0.0.Final or later**.\n\nIf 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.\n\n### Workarounds\n\nNone (other than doing your own build).\n\n### References\n\n* https://github.com/advisories/GHSA-c5hg-mr8r-f6jp","status":"published","published":"2022-12-30T22:13:59Z","modified":"2024-12-02T05:52:25.904646Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:46:53.700556Z"}]}}