Skip to content
Fencer Vulns
medium 6.5

CVE-2017-2638 json

Infinispan Rest API Does Not Enforce Auth Constraints

published 2018-07-16 8 y ago modified 2026-06-17 4 mo ago also GHSA-mvxp-3j62-jqr6 , EUVD-2022-4631

cvss
6.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

It was found that the REST API in Infinispan before version 9.0.0 did not properly enforce auth constraints. An attacker could use this vulnerability to read or modify data in the default cache or a known cache name.

Patch / fix

  • maven org.infinispan:infinispan-server-core 9.0.0
  • infinispan infinispan 9.0.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2638 updated cvss 6.5

infinispan: auth bypass in REST api

  • Red Hat JBoss Data Grid 6 rest
    affected: no fix available
  • Red Hat JBoss Data Grid 7.1
    fixed: vendor fix RHSA-2017:1097

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.infinispan:infinispan-server-core
<9.0.0
9.0.0

Affected products

  • [UNKNOWN] infinispan

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality
  • CWE-287 Improper Authentication

References

Sources

Fencer Vulns 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.