Skip to content

← Public intelligence

Maven package

org.infinispan:infinispan-core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

7 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.1MavenPublished

    Infinispan caches credentials in clear text

    CVE-2023-5384 · GHSA-gg57-587f-h5v6

    Affected
    • Maven org.infinispan:infinispan-core >= 15.0.0.Dev01, < 15.0.0.Dev07; < 14.0.25.Final
    Fixed in
    15.0.0.Dev0714.0.25.Final· Vendor fix available
    Issue
    A flaw was found in Infinispan. When serializing the configuration for a cache to XML/JSON/YAML, which contains credentials (JDBC store with connection pooling, remote store), the credentials are returned in clear text as part of the configuration.

    Recommended action: Upgrade to 15.0.0.Dev07 or 14.0.25.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Use of Externally-Controlled Input to Select Classes or Code in Infinispan

    CVE-2019-10174 · GHSA-h47x-2j37-fw5m

    Affected
    • Maven org.infinispan:infinispan-core <= 8.2.11.Final; >= 9.0.0.Final, <= 9.4.16.Final
    Fixed in
    9.4.17.Final8.2.12.Final· Vendor fix available
    Issue
    A vulnerability was found in Infinispan such that the invokeAccessibly method from the public class ReflectionUtil allows any application class to invoke private methods in any class with Infinispan's privileges. The attacker can use reflection to introduce new, malicious behavior into the application.

    Recommended action: Upgrade to 9.4.17.Final or 8.2.12.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 8.8MavenPublished

    Deserialization of Untrusted Data in Infinispan

    CVE-2017-15089 · GHSA-46r5-59fg-2fjc

    Affected
    • Maven org.infinispan:infinispan-core <= 9.2.0.Beta2
    Fixed in
    9.2.0.CR1· Vendor fix available
    Issue
    It was found that the Hotrod client in Infinispan before 9.2.0.CR1 would unsafely read deserialized data on information from the cache. An authenticated attacker could inject a malicious object into the data cache and attain deserialization on the client, and possibly conduct further attacks.

    Recommended action: Upgrade to 9.2.0.CR1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. High, CVSS 8.8MavenPublished

    Infinispan: Deserialization of untrusted data in the Hot Rod Java client via automatic byte-array deserialization

    CVE-2016-0750 · GHSA-4hhg-8ghq-vwq6

    Affected
    • Maven org.infinispan:infinispan-core < 9.1.0.Final
    Fixed in
    9.1.0.Final· Vendor fix available
    Issue
    The hotrod java client in infinispan before 9.1.0.Final automatically deserializes bytearray message contents in certain events. A malicious user could exploit this flaw by injecting a specially-crafted serialized object to attain remote code execution or conduct other attacks.

    Recommended action: Upgrade to 9.1.0.Final or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. High, CVSS 8.8MavenPublished

    Deserialization of Untrusted Data in Infinispan

    CVE-2018-1131 · GHSA-qqfc-m9hc-pqv3

    Affected
    • Maven org.infinispan:infinispan-core >= 8.2.10.Final, <= 8.2.10.Final; >= 9.0.3.Final, <= 9.0.3.Final; >= 9.1.7.Final, <= 9.1.7.Final; >= 9.2.2.Final, <= 9.2.2.Final; >= 9.3.0.Alpha1, <= 9.3.0.Alpha1
    Fixed in
    9.3.1.Final· Partial vendor fix
    Issue
    Infinispan permits improper deserialization of trusted data via XML and JSON transcoders under certain server configurations. A user with authenticated access to the server could send a malicious object to a cache configured to accept certain types of objects, achieving code execution and possible further attacks. Versions 9.0.3.Final, 9.1.7.Final, 8.2.10.Final, 9.2.2.Final, 9.3.0.Alpha1 are believed to be affected.

    Recommended action: Upgrade to 9.3.1.Final; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  6. Medium, CVSS 6.5MavenPublished

    Improper Access Control in infinispan-server-runtime

    CVE-2020-25711 · GHSA-8674-26jc-wh98

    Affected
    • Maven org.infinispan:infinispan-core <= 11.0.5.Final
    Fixed in
    11.0.6.Final· Vendor fix available
    Issue
    A flaw was found in infinispan 10 REST API, where authorization permissions are not checked while performing some server management operations. When authz is enabled, any user with authentication can perform operations like shutting down the server without the ADMIN role.

    Recommended action: Upgrade to 11.0.6.Final or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  7. Critical, CVSS 9.8MavenPublished

    Improper implementation of the session fixation protection in Infinispan

    CVE-2019-10158 · GHSA-6x3v-rw2q-9gx7

    Affected
    • Maven org.infinispan:infinispan-core < 9.4.15.Final
    Fixed in
    9.4.15.Final· Vendor fix available
    Issue
    A flaw was found in Infinispan through version 9.4.14.Final. An improper implementation of the session fixation protection in the Spring Session integration can result in incorrect session handling.

    Recommended action: Upgrade to 9.4.15.Final or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →