# CVE-2023-3629: Infinispan: non-admins should not be able to get cache config via rest api

> Authenticated users can access cache configuration data via REST API without admin permissions, leading to unauthorized information disclosure.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Dec 2023
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-r4w2-hjmr-36m7

## What is CVE-2023-3629?

CVE-2023-3629 is a medium-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 18 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Infinispan's REST, Cache retrieval endpoints do not properly evaluate the necessary admin permissions for the operation. This issue could allow an authenticated user to access information outside of their intended permissions.

Weakness: CWE-304 (Missing Critical Step in Authentication)

## Which versions are affected by CVE-2023-3629?

4 open source packages ship an affected version, including org.infinispan:infinispan-server-rest. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.infinispan:infinispan-server-rest` | Maven | All versions | 14.0.18.Final |
| `org.infinispan:infinispan-server-rest` | Maven | All versions | 14.0.18.Final |
| `org.infinispan:infinispan-server-rest` | Maven | From 15.0.0.Dev01 | 15.0.0.Dev04 |
| `org.infinispan:infinispan-server-rest` | Maven | From 15.0.0.Dev01 | 15.0.0.Dev04 |

Products: Infinispan Infinispan, Redhat Data Grid, Redhat Jboss Data Grid, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2023-3629?

Upgrade org.infinispan:infinispan-server-rest to a fixed version for your release line: 14.0.18.Final or 15.0.0.Dev04.

## Is CVE-2023-3629 being exploited?

There is no known exploitation of CVE-2023-3629 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2018-1131](https://insights.sbomify.com/CVE-2018-1131/): Deserialization of Untrusted Data in Infinispan (high 8.8)
- [CVE-2017-15089](https://insights.sbomify.com/CVE-2017-15089/): Deserialization of Untrusted Data in Infinispan (high 8.8)
- [CVE-2019-10174](https://insights.sbomify.com/CVE-2019-10174/): Use of Externally-Controlled Input to Select Classes or Code in Infinispan (high 7.5)
- [CVE-2023-5384](https://insights.sbomify.com/CVE-2023-5384/): Infinispan: credentials returned from configuration as clear text (high 7.2)
- [CVE-2023-3628](https://insights.sbomify.com/CVE-2023-3628/): Infispan: rest bulk ops don't check permissions (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3629 and fix it if it is affected.

What it is: CVE-2023-3629 is a medium-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 18 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3629 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.infinispan:infinispan-server-rest (Maven): affected all versions; fixed in 14.0.18.Final
- org.infinispan:infinispan-server-rest (Maven): affected all versions; fixed in 14.0.18.Final
- org.infinispan:infinispan-server-rest (Maven): affected from 15.0.0.Dev01; fixed in 15.0.0.Dev04
- org.infinispan:infinispan-server-rest (Maven): affected from 15.0.0.Dev01; fixed in 15.0.0.Dev04

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/CVE-2023-3629/ (Markdown: https://insights.sbomify.com/CVE-2023-3629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3629
- OSV: https://osv.dev/vulnerability/CVE-2023-3629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3629/
Summaries are generated and may contain mistakes; the official description above is the record.